This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#elements-in-the-dom Complete: https://html.spec.whatwg.org/#elements-in-the-dom Referrer: Comment: Need to define what "defined by this specification" means Posted from: 98.110.194.132 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Firefox/38.0
For as specific example, is <basefont> defined or not? That is, should it be HTMLElement or HTMLUnknownElement? What UAs do is: IE11: HTMLBaseFontElement Safari/WebKit: HTMLBaseFontElement Chrome: HTMLElement Firefox: HTMLSpanElement I'm going to assume this one is "defined" and HTMLElement and change Firefox accordingly, seeing as it has parsing and rendering rules, but it would be good to clarify this, since whoever wrote the web platform test seems to think it should be HTMLUnknownElement.
Maybe clarify it by pointing to the obsolete section and how it applies for this requirement? It's "defined" here: https://html.spec.whatwg.org/multipage/obsolete.html#basefont Also note: "The blink, bgsound, isindex, multicol, nextid, rb, and spacer elements must use the HTMLUnknownElement interface." HTMLSpanElement seems bogus, but any of HTMLBaseFontElement, HTMLElement or HTMLUnknownElement seem reasonable. The spec currently requires HTMLElement AFAICT.
Domenic, this seems relevant for your "element interface" rewrite.
Will be defined better in https://github.com/whatwg/html/pull/1012; see also https://github.com/whatwg/html/issues/1015 for discussion of some potential compat-motivated changes.