On Thu, 12 Mar 2009 10:47:53 -0400, Alexey Proskuryakov wrote:
12.03.2009, в 17:19, Lachlan Hunt написал(а):
WebKit has a bug with the "|foo" selector.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/28
Opera and Firefox pass
This is actually a difference in createElementNS(
12.03.2009, в 18:01, Boris Zbarsky написал(а):
Make of this what you will. But as I recall, the change in the "XML
Namespaces" section was meant precisely to ensure that in JS passing
"" for all namespace URIs would work exactly like passing null.
Sounds like webkit either implements crea
Lachlan Hunt wrote:
Interestingly, though, Opera has the opposite bug. We fail when null is
passed instead of "".
Fun. Maybe the test should just test both. ;)
-Boris
Alexey Proskuryakov wrote:
This is actually a difference in createElementNS(null, "p") vs.
createElementNS("", "p") behavior. I don't know whose bug it is, but in
Firefox and Opera, empty and null namespace arguments both result in
null namespace for the created element.
Interesting question.
Alexey Proskuryakov wrote:
12.03.2009, в 17:19, Lachlan Hunt написал(а):
WebKit has a bug with the "|foo" selector.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/28
Opera and Firefox pass
This is actually a difference in createElementNS(null, "p") vs.
createElementNS("", "p")
12.03.2009, в 17:19, Lachlan Hunt написал(а):
WebKit has a bug with the "|foo" selector.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/28
Opera and Firefox pass
This is actually a difference in createElementNS(null, "p") vs.
createElementNS("", "p") behavior. I don't know w
Lachlan Hunt wrote:
Hi,
The Selectors API test suite is missing tests for the namespace
selectors "|foo" and "*|foo". Since they don't have prefixes that need
to be resolved, they should be supported even without an NSResolver.
WebKit has a bug with the "|foo" selector.
http://software.hi
Hi,
The Selectors API test suite is missing tests for the namespace
selectors "|foo" and "*|foo". Since they don't have prefixes that need
to be resolved, they should be supported even without an NSResolver.
See brief IRC discussion about this:
http://krijnhoetmer.nl/irc-logs/whatwg/2009031
