- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 6 Apr 2009 13:51:12 -0700
On Mon, Apr 6, 2009 at 11:33 AM, Giovanni Campagna <scampa.giovanni at gmail.com> wrote: > 2009/4/6 Ojan Vafai <ojan at chromium.org>: >> On Fri, Apr 3, 2009 at 10:46 PM, Cameron McCormack <cam at mcc.id.au> wrote: >>> >>> Ojan Vafai: >>> > 2) Add a css or xpath expression to fragment identifiers. Tthe iframe >>> > src can be set to http://foo.com#css(.foo #bar). Same as above >>> > applies. If there's no match, it's a noop. If there is a match, it >>> > scrolls the first one into view. >>> >>> Sounds like XPointer: >>> >>> ?http://www.w3.org/TR/xptr-framework/ >> >> Yes, it's a similar idea. XPointer seems focused on XML/XHTML, I'm not sure >> what it would take to extend the spec to include HTML. In addition, I don't >> really see the point of adding yet another element addressing scheme to the >> web. XPath and CSS selectors are already there and familiar to developers. > > Actually, XPointer is just the application of XPath in fragment > identifiers of XML resources, but it is designed in a way that could > allow a "css" scheme or anything else, if specified. >From my point of view I'm not sure how interesting this whole feature is. We had support in firefox for XPointer for many years and saw little to no uptake. I'm not sure if anyone complained when we removed the support even (which would be pretty remarkable). / Jonas
Received on Monday, 6 April 2009 13:51:12 UTC