Open ricardoboss opened 2 years ago
Seems like it'll be a while until WebKit supports it, so we should probably go with the first for now?
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.
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.