Only unknown elements should implement HTMLUnknownElement

RESOLVED FIXED in mozilla5

Status

()

defect
RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: Ms2ger, Assigned: Ms2ger)

Tracking

({html5})

Trunk
mozilla5
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Posted patch Patch v1 (obsolete) — Splinter Review
Also, it doesn't make sense to let it inherit from nsHTMLSpanElement. Patch attached.
Attachment #464394 - Flags: review?(Olli.Pettay)
Comment on attachment 464394 [details] [diff] [review]
Patch v1

I think we should do this, but Jonas should review this too, since he
actually removed nsHTMLUnknownElement in Bug 236873 (though that patch
left a bug in QI implementation: unknown element can be Qied to spanelement).
Attachment #464394 - Flags: review?(jonas)
Attachment #464394 - Flags: review?(Olli.Pettay)
Attachment #464394 - Flags: review+
Comment on attachment 464394 [details] [diff] [review]
Patch v1

Looks good, you should write tests though.
Attachment #464394 - Flags: review?(jonas) → review+
Assignee

Comment 3

9 years ago
Adding to test_bug389797.html gets me better coverage than writing up another test, I think.
Oh, sorry, missed that you had. Carry on then. As you were.
Assignee

Comment 5

9 years ago
The hunk is well hidden :)

I'll try to get this landed after braching.
Whiteboard: [needs landing]
Assignee

Updated

9 years ago
Depends on: post2.0
Assignee

Comment 6

8 years ago
Attachment #464394 - Attachment is obsolete: true
Assignee

Updated

8 years ago
Keywords: checkin-needed
Whiteboard: [needs landing]
http://hg.mozilla.org/mozilla-central/rev/9969f1d12e17
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.2
You need to log in before you can comment on or make changes to this bug.