- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Nov 2014 15:48:04 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27384 --- Comment #9 from Philip Jägenstedt <philipj@opera.com> --- (In reply to Boris Zbarsky from comment #8) > > Is there a tracking bug for that? > > I don't know. Simon, do you know which spec and browser bugs are relevant to this? > > so kicking @namespace and @charset out of CSSOM and implementations seems > > feasible. > > I'm 99% sure there is stuff depending on existence of @namespace rules, at > least (e.g. editors built on top of browser engines). Not web content, but > not things we really want to break nevertheless. At least in my opinion. Here's a quick test: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3314 It looks like WebKit/Blink are the only to not represent it. Blink bug: https://code.google.com/p/chromium/issues/detail?id=389549 Gecko doesn't have the CSSNamespaceRule interface, but instead CSSNameSpaceRule... Simon, do you care whether CSSNamespaceRule lives or dies? Is it in the same bucket as CSSCharsetRule or does it actually make sense? > > it seems plausible that making insertRule(rule) with no index append > > instead of prepend would work > > Maybe. What should insertRule(rule, undefined) do? Right now it prepends > in all UAs, right? Per WebIDL trailing undefined arguments are treated as missing arguments, so I don't think this will be a problem. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 November 2014 15:48:06 UTC