Need to handle classes like <cite> that lack their own Element subclasses more cleanly

[jacob314]

Need to handle classes like <cite> that lack their own Element subclasses more cleanly
Currently we have to define a hack class called _HTMLElementImpl.
If frog supported
native "*Element,*HTMLElement"
syntax we could clean this up.

[rakudrama]

I think the current 'hack class' is fine.
You are defining the behaviour of a (hidden native) class with the tag 'HTMLElement' by nominating some superclass and saying the behaviour is the same as that superclass.

I think we will find there are some problems with the proposed 'native "*Element,*HTMLElement"' feature.
For one, the feature demands that we somehow define the methods on two tags, but we don't want the code bloat from duplicating the definitions by 'applying' them to two tags.

I think the 'hack class' is probably the lesser evil.

 

---

Removed Priority-Medium label.
Added Priority-Low label.

[vsmenon]

Removed Area-UI label.
Added Area-DOM label.

[vsmenon]

Added this to the Later milestone.

[iposva-google]

Removed Area-DOM label.
Added Area-HTML label.

[vsmenon]

Removed the owner.

[blois]

Issue #4418 has been merged into this issue.

[DartBot]

This comment was originally written by tylerbthrai...@gmail.com

---

Does this also apply to the <code> tag?

[kevmoo]

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

[kasperl]

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

[kasperl]

Removed Oldschool-Milestone-Later label.

[alan-knight]

This is clearly not happening soon, and it's not clear if it's even desirable. Let's close and if it re-emerges with more context we can re-examine.

---

Added WontFix label.

[alan-knight]

Issue #16275 has been merged into this issue.