We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, when clicking on a search result, it just takes the user to the page itself, not the part where the search term is located.
As I see it currently, we have two options to improve the users experience:
The second option is only supported in chromium-based browsers.
The text was updated successfully, but these errors were encountered:
Seems like it'll be a while until WebKit supports it, so we should probably go with the first for now?
Sorry, something went wrong.
What about a feature switch based on the detected browser? Implement both and choose at runtime?
We can do that, but you'd have to hardcode user agents. (FWIW, Mozilla doesn't seem to be sure yet if a competing spec is better: https://mozilla.github.io/standards-positions/#fragmention)
Yeah ok, might better to stick to the standards on this one. So nearest parent heading it is?
Yeah, IMHO, just go with nearest for now and reëvaluate in a year or so.
When branches are created from issues, their pull requests are automatically linked.
Currently, when clicking on a search result, it just takes the user to the page itself, not the part where the search term is located.
As I see it currently, we have two options to improve the users experience:
The second option is only supported in chromium-based browsers.
The text was updated successfully, but these errors were encountered: