[Webkit-unassigned] [Bug 135698] SVGElement has no innerHTML property

[bugzilla-daemon at webkit.org]

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





--- Comment #13 from Caitlin Potter <caitpotter88 at gmail.com>  2014-09-10 06:40:35 PST ---
(In reply to comment #11)
> (In reply to comment #10)
> > fwiw, the webkit treatment appears to be spec-correct, but I would treat it as a bug due to being incompatible with 2 major vendors.
> 
> It's no more correct. The spec has been fixed last year [1]. innerHTML is now defined on Element (implemented in Chrome [2] and Firefox) *and* should create elements with correct namespace (ok in chrome [2], not yet in Firefox [3]).
> 
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17924
> [2] https://code.google.com/p/chromium/issues/detail?id=311080
> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=886390

Not according to any of the DOM specs which have made it to REC, or the WHATWG's DOM.

However, this is academic, because if 2 major vendors are exposing this on Element, then it really doesn't matter what the spec says.

(In reply to comment #12)
> Testcase (http://marianoguerra.github.io/bugs/svgbug/) from the following issue on Github: https://github.com/facebook/react/issues/1900 .
> Webkit is also impacted as innerHTML is not defined on SVG elements.
> 
> Only the second example ("innerHTML") is relevant here. 
> It is certainly more complicated than just define innerHTML on Element because it should also create the <text> node as SVGTextElement and not as HTMLUnknownElementPrototype.

Yes, it's obviously necessary to use the correct parsing insertion mode. By "not terribly difficult" I'm not saying it's a one-line patch, just that it's clear what is needed to be done.

Would you care to write the patch? I will not have time for at least 2 weeks.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.