Closed
Bug 1775477
Opened 3 years ago
Closed 3 years ago
Should keygen be an HTMLElement or an HTMLUnknownElement?
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
FIXED
103 Branch
Tracking | Status | |
---|---|---|
firefox103 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(2 files)
Right now it's the former, but if we regenerate ElementName.java
we get the later. I manually changed it back in bug 1372276 but we should figure out what's the right thing to do and either fix nsHTMLTags.h or the parser.
Comment 1•3 years ago
|
||
document.createElement("keygen").constructor.name
is already HTMLUnknownElement
while document.createRange().createContextualFragment("<keygen>").children[0].constructor.name
is HTMLElement
.
Other elements in https://html.spec.whatwg.org/multipage/obsolete.html#non-conforming-features gives HTMLUnknownElement
for both, so I believe unknown is the right way.
Assignee | ||
Comment 2•3 years ago
|
||
Yes, I agree.
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•3 years ago
|
||
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1865e24c6775
Fix interface for parser-created <keygen> elements. r=saschanaz
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/34547 for changes under testing/web-platform/tests
Comment 7•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox103:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•