You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scroll to selector extension to the scroll-to-text-fragment explainer we propose adding a fragment directive which selects elements. When we scroll to these, as with scrolling to text, there is a desire to have a default style which calls attention to the element. In this particular case an outline is the current leading proposal.
As with scroll-to-text issue #5522, this style should be customizable by the developer. Semantically, the :target pseudoclass perfectly describes this target, however adding a default UA style to outline targeted elements would affect the style of existing anchor fragment navigation elements in an undesirable way.
This leads to the question in the issue, do we need a new pseudoclass for these targets? Or, should we use :target, and if so is there a way to ensure the default UA style for fragment directive targets is not applied on anchor navigation? With :target-text we had no issues as this was an entirely new concept and so would not have existing styles or navigation cases which activated it.
The text was updated successfully, but these errors were encountered:
In the scroll to selector extension to the scroll-to-text-fragment explainer we propose adding a fragment directive which selects elements. When we scroll to these, as with scrolling to text, there is a desire to have a default style which calls attention to the element. In this particular case an outline is the current leading proposal.
As with scroll-to-text issue #5522, this style should be customizable by the developer. Semantically, the :target pseudoclass perfectly describes this target, however adding a default UA style to outline targeted elements would affect the style of existing anchor fragment navigation elements in an undesirable way.
This leads to the question in the issue, do we need a new pseudoclass for these targets? Or, should we use :target, and if so is there a way to ensure the default UA style for fragment directive targets is not applied on anchor navigation? With :target-text we had no issues as this was an entirely new concept and so would not have existing styles or navigation cases which activated it.
The text was updated successfully, but these errors were encountered: