Bug 100841 - Allow CSS selectors as fragment identifiers
Summary: Allow CSS selectors as fragment identifiers
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P3 Enhancement
Assignee: Nobody
URL: http://simonstl.com/articles/cssFragI...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-31 04:24 PDT by John Mellor
Modified: 2012-11-01 02:35 PDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Mellor 2012-10-31 04:24:35 PDT
It would be nice to allow using CSS selectors as fragment identifiers, so that you can link to things which don't have an id or name attribute. For example:

http://example.com/lorem.html#css(.content:nth-child(2))

There's an unofficial draft spec: http://simonstl.com/articles/cssFragID.html
And a community group: http://www.w3.org/community/cssselfrags/

The main downside I can see is that such fragments may be brittle and break if the structure of the page is changed, but this is often still preferable to not being able to use a fragment at all.
Comment 1 Maciej Stachowiak 2012-11-01 02:35:00 PDT
It's an interesting idea. Are there any other browser engines planning to implement this? Are there any plans to move this work into a full Working Group?