The explainer references content-visibility: hidden-matchable, but that
value isn't in the draft spec .
What is the relationship between content-visibility and beforematch?
On 5/2/20 12:36 AM, Joey Arhar wrote:
> Contact emails...@chromium.org
> docs/specNo design doc
> beforematch event allows developers to display content to the user in
> response to the following actions: - find-in-page (ctrl+f) - element
> fragment navigation (example.com/#foo
>) The event is fired at render timing
> before these actions scroll the page. The event is fired on the element
> which contains the text, or in the case of element fragment navigation,
> whichever element has the target id. MotivationWith the evolution of the
> beforematch. /Firefox/: No public signals /Edge/: No public signals
> /Safari/: No public signals /Web developers/: No signals Ergonomics This
> API is likely to be used in tandem with display locking AKA
> content-visibility: https://github.com/WICG/display-locking
> I don't foresee any
> performance issues with using beforematch at the moment. Activation This
> feature will benefit from having example code in the explainer repo to
> show developers how to use it. Security I don't have any security
> considerations for this feature.
> DebuggabilityThere are no DevTools features for the scrolling, URL
> fragment, and event firing impacts that beforematch has. Will this
> feature be supported on all six Blink platforms (Windows, Mac, Linux,
> Chrome OS, Android, and Android WebView)?Yes Is this feature fully
> tested by web-platform-tests
> You received this message because you are subscribed to the Google
> Groups "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to blink-dev+...@chromium.org