Re: [w3ctag/design-reviews] Scroll To Text (#392)

Based on URI feedback, we've updated our proposal to use a fragment directive delimiter that is valid by URL spec, `:~:` instead of `##`. This means we only need to amend HTML spec to allow `:~:` to indicate the fragment directive.

> I'm a bit worried about interop here. Are you effectively requiring all browser engines to use ICU? If not, how can we ensure interoperability in a world where the word dictionary isn't specified / standardized? This is especially concerning given that the quality of word boundary analysis directly affects the efficacy of a security mitigation in this spec.

We improved our spec on word boundary matching based on your feedback and discussion with @domenic: https://wicg.github.io/ScrollToTextFragment/#next-word-bounded-instance


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/392#issuecomment-539605201