On Nov 26, 2009, at 15:07 , Lachlan Hunt wrote:
Jonathan Watt wrote:
Nevertheless, that doesn't mean that Web
content shouldn't be able to process XML that uses xml:id using script and
present the processed information to the user using content and semantics
that
*does* belong on the Web.
Robin Berjon wrote:
On Nov 26, 2009, at 15:07 , Lachlan Hunt wrote:
Jonathan Watt wrote:
Nevertheless, that doesn't mean that Web content shouldn't be
able to process XML that uses xml:id using script and present the
processed information to the user using content and semantics
that *does*
On Nov 30, 2009, at 15:38 , Lachlan Hunt wrote:
The lack of namespace resolution in selectors is extremely annoying
because it means that one has to switch between selectors (if only
for classes support) and the XPath APIs for namespace support
whenever one tries to do, you know, one of those
Robin Berjon wrote:
There are quite a few services out there that return XML — it would
be disingenuous to pretend otherwise. The addition of x-site requests to
the stack makes these even more available. XHR supports XML natively,
including namespace. Selectors support namespaces natively.
On Nov 26, 2009, at 13:18, Jonathan Watt wrote:
During a discussion about xml:id I was about to make the throw away comment
that
you could use querySelector to easily work around lack of support for xml:id,
but on checking it turns out that's not the case. querySelector, it seems,
cannot be
On Thu, 26 Nov 2009 09:33:28 -0200, Henri Sivonen hsivo...@iki.fi wrote:
On Nov 26, 2009, at 13:18, Jonathan Watt wrote:
[...]
Isn't the easiest solution not to support xml:id on the Web? It's not
supported in Gecko, WebKit or Trident. What's the upside of adding it?
Besides that,
Jonathan Watt wrote:
During a discussion about xml:id I was about to make the throw away comment that
you could use querySelector to easily work around lack of support for xml:id,
but on checking it turns out that's not the case. querySelector, it seems,
cannot be used to select on a specific
On 2009-11-26 12:33 PM, Henri Sivonen wrote:
On Nov 26, 2009, at 13:18, Jonathan Watt wrote:
During a discussion about xml:id I was about to make the throw away comment
that
you could use querySelector to easily work around lack of support for xml:id,
but on checking it turns out that's
On 2009-11-26 1:16 PM, Lachlan Hunt wrote:
Jonathan Watt wrote:
Maybe the working group could consider adding some sort of non-prefix
namespace support to selectors for the sake of
querySelector/querySelectorsAll,
something like:
[url(http://www.w3.org/XML/1998/namespace;)|id=foo]
On 2009-11-26 2:16 PM, Jonathan Watt wrote:
On 2009-11-26 1:16 PM, Lachlan Hunt wrote:
Jonathan Watt wrote:
Maybe the working group could consider adding some sort of non-prefix
namespace support to selectors for the sake of
querySelector/querySelectorsAll,
something like:
Jonathan Watt wrote:
On 2009-11-26 12:33 PM, Henri Sivonen wrote:
On Nov 26, 2009, at 13:18, Jonathan Watt wrote:
During a discussion about xml:id I was about to make the throw away comment that
you could use querySelector to easily work around lack of support for xml:id,
but on checking it
11 matches
Mail list logo
