- From: Mike Schinkel <w3c-lists@mikeschinkel.com>
- Date: Sat, 28 Apr 2007 04:04:52 -0400
- To: Maciej Stachowiak <mjs@apple.com>
- CC: public-html@w3.org
Maciej Stachowiak wrote: > > I imagine XPointer would work on the DOM, so it doesn't matter how the > document was initially parsed. I think it would be incredibly beneficial if some method were made that would allow for use of (something) XPointer(-like) in browsers today. > > (Side note: when people here say "tag soup" do they mean > "non-conforming HTML" or "any HTML"? I can't really tell from general > usage of the term. I always assumed it specifically meant > non-conforming or otherwise "bad" markup, but people seem to use it as > a dismissive way to refer to anything in HTML syntax.) Can't speak for others, but I meant "non-conforming HTML", but since you can't generically know which is which form a URL, it is effectively "any HTML." > >> And is what use is it (in the HTMLWG context) if neither IE7 nor >> FF2 see fit to implement it? >> Shouldn't it be better to look at something that would become part of >> the HTML spec? > > I'd guess if browsers have not implemented it, it's because they have > not seen significant demand for anything but id (or anchor name) > fragment addressing, not because they dislike the syntax details. So I > don't think designing a second technology to do the same thing would > be helpful. Oh, I'm not suggesting a new technology, just that if it can be implemented that it is implemented. What I'd especially like is something that can be used to identify not just a location in a document put also a segment of a document and maybe browsers could implement displaying the rest of the document in a reserve highlight. -- -Mike Schinkel http://www.mikeschinkel.com/blogs/ http://www.welldesignedurls.org http://atlanta-web.org - http://t.oolicio.us
Received on Saturday, 28 April 2007 08:05:14 UTC