- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Oct 2012 08:32:46 +0000
- To: public-webapps-bugzilla@w3.org
- Message-ID: <bug-19431-2532-2MQZWnO5JW@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19431 --- Comment #10 from Aryeh Gregor <ayg@aryeh.name> --- (In reply to comment #8) > You are forgetting about developers though. Having different behavior for > MIME types while effectively we treat all XML MIME types equal in most > places is super weird. Which developers, the three who serve stuff with an XML MIME type? > image/svg+xml and application/mathml+xml also seem > relevant to test. Okay, will do. > As well as scripts running in image/jpeg derived HTML > documents and such (see page loading in HTML). How does that work? This doesn't seem to allow author scripts to run in image/jpeg-derived HTML documents: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#read-media Or did you mean something else? > Overall though, very much opposed to making this simple method very complex. Me too, but making it a bit more complex doesn't seem like it should be a big deal -- not if it's just adding a switch on .contentType. (In reply to comment #9) > Removing the xmlns attribute doesn't change the namespace of the root > element. > > http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1838 > > > In Opera it's > > dependent on the namespace of the initial root element, regardless of MIME > > type. > > s/initial/current/ Ah, thanks for the pointer. Noted. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 14 October 2012 08:32:48 UTC