- From: Buck Golemon <buck@yelp.com>
- Date: Mon, 29 Jul 2013 13:05:46 -0700
- To: public-qt-comments <public-qt-comments@w3.org>
Received on Thursday, 1 August 2013 09:20:47 UTC
In the meantime, I've verified that chrome, internet explorer 10, and libxml2 all return (forcefully) lower-cased strings from fn:name(). Here is a minimal, reproducible test case: http://fiddle.jshell.net/J7VrG/8/show/light/ On Mon, Jul 29, 2013 at 11:56 AM, Buck Golemon <buck@yelp.com> wrote: > It's come to my attention recently that Firefox returns upper-cased > strings from the xpath name() function, while other implementations I've > surveyed return a not-upper-cased string (I haven't yet checked whether > they are forcefully lower-cased or simply untouched). > > Is one of these implementations out of spec? > > I'd like to bring this inconsistency to the attention of implementers and > ask them to "fix" it, but I'd want to bring them a definitive specification > of Correct behavior. > > If anyone requests a thorough survey of implementation behavior (in > regards to fn:name() return value casing) I will do so. > > -buck >
Received on Thursday, 1 August 2013 09:20:47 UTC