Inconsistent behavior - Githubissues

WICG / scroll-to-text-fragment

Proposal to allow specifying a text snippet in a URL fragment

Other

589 stars 42 forks source link

Inconsistent behavior #114

Closed tomcritchlow closed 4 years ago

tomcritchlow commented 4 years ago

Hey there - I'm seeing very inconsistent and sometimes sporadic behavior with scrolltotextfragment. Can you shed some light on this?

I'm seeing:

Sometimes the text is not highlighted and nothing happens
Sometimes the text is highlighted but no scroll happens
Sometimes you need to refresh the page to see anything happen

And - most puzzling is that some URLs work sometimes and not other times. This makes testing and debugging incredibly difficult...

A few examples:

This one works for me

While

This one does nothing

Am I constructing these incorrectly? Why am I seeing inconsistent behavior?

atjn commented 4 years ago

Hmmm. Both of those links work perfectly fine for me in Chrome 83 on Windows 10. In my experience, the feature has worked consistently for everything i used it for.

What is your specific setup? It sounds to me like this is a setup-specific issue that should be fixed in a chromium bug, not in the spec.

bokand commented 4 years ago

They both work for me too and +1 about filing on crbug.com/ for implementation issues.

that said, there's a few security based reasons we might avoid invoking the fragment, maybe you were hitting those between runs? the main one I can think of is if you have a popup and try the link cross-origin.

Another case is if you're clicking links from apps/pages that use a redirector (e.g. Twitter's t.co redirector). Those will fail because the redirect doesn't propagate a user activation.

In any case, if you're still having issues feel free to file a bug with details in crbug.com/new and we can followup there.