This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23161 - [Shadow]: url fragment identifiers should be followed into ShadowDOM
Summary: [Shadow]: url fragment identifiers should be followed into ShadowDOM
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 28552
  Show dependency treegraph
 
Reported: 2013-09-05 02:16 UTC by Steve Orvell
Modified: 2015-05-27 03:22 UTC (History)
2 users (show)

See Also:


Attachments

Description Steve Orvell 2013-09-05 02:16:51 UTC
Given the following: 

1. a user navigates to: foo.com/#footer

2. at the requested url inside some shadowRoot we have:
<div>
SR
  <footer id="footer"></footer>

In this case, the #footer resource should be navigated to (page scrolls to it) even though it is inside a shadowRoot. There is one url for a page and it must be shared by all the shadowRoots. 

Since id's are scoped inside ShadowDOM, there may be a lot of duplicates page-wide. So, which one should be followed? The answer here is to do what browsers do now in this case: navigate to the first fragment identifier.
Comment 1 Hayato Ito 2015-05-27 03:22:04 UTC
Moved to https://github.com/w3c/webcomponents/issues/66