518110 - nuke HTMLBaseFontElement interface

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Anne (:annevk)]

Opera recently removed rendering support for the <basefont> element to be in line with Gecko/WebKit, but the interface is still there because it is still in Gecko/WebKit. Would it be possible to clean this up or are we forever stuck with it? (I realize we're forever stuck with the quirk in the parser.)

Comment 1

[Anne (:annevk)]

WebKit: https://bugs.webkit.org/show_bug.cgi?id=29641

Comment 2

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Attachment: Patch to fix

This patch does a few things

* Remove the nsIDOMHTMLBaseFontElement interface and tests for it.
* Remove (or rather make non-scriptable in order to preserve binary compat)
  nsIDOMHTMLHeadElement.profile. This is largely useless and I think it can
  be removed from the HTML5 spec.
* Kill nsHTMLHeadElement and nsHTMLHtmlElement. Instead use nsHTMLSharedElement
  for these element types.
* Remove apparently bogus comment about keeping classinfo ids stable

Comment 3

[Johnny Stenback (:jst)]

Comment on attachment 437807 [details] [diff] [review]
Patch to fix

r=jst!

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Checked in

http://hg.mozilla.org/mozilla-central/rev/3a2552c83446