-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track hashchange
event
#136
Comments
My guess is that the polyfill should match Chrome's behavior, so the PR is here: #137. |
I noticed this as well in Firefox by just changing the |
@bokand, what do you think is the right behavior here? |
There's some context in WICG/scroll-to-text-fragment#74 Given the way STTF is spec'd and implemented, a hash change should cause a scroll-to-text since it invokes the "scroll to the fragment" algorithm which is where STTF is invoked. |
Any reason why this is not merged yet? |
Apologies for the delay - looks good with a comment I left on the review. |
Sorry - I forgot to hit "submit". You should see it now |
In Chrome, if you set a new text fragment hash programmatically, like
https://github.com/GoogleChromeLabs/text-fragments-polyfill
location.hash = '#:~:text=module%20of%20util-,functions,-for%20generating%20URLs';
, the page will be scrolled to the text.
The behavior does not provide such functionality.
The text was updated successfully, but these errors were encountered: