Re: [w3ctag/design-reviews] Display Locking (#306)

With regards to `beforematch`:

1. It does not allow searching for any content that isn't in the DOM. However, the content that is included in the DOM can be excluded from rendering by the user-agent (e.g. in a collapsed section). The beforematch can search some of these sections and send an event allowing the developer to show the content (e.g. expand the section).
2. `hashchange` seems to be an event that is tied to the fragment identifier changing. I think that can replace the fragment-link navigation part (one out of three cases) with the caveat that the script would need to parse the url fragment to find out the element id. It does not address find-in-page or scroll-to-text navigation (at least, not to my knowledge).

-- 
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/306#issuecomment-594144559