Contact emailsmas...@chromium.org, chrom...@keithcirkel.co.uk Explainerhttps://open-ui.org/components/interest-invokers.explainer
Specificationhttps://github.com/whatwg/html/pull/11006 Summary This feature adds an `interesttarget` attribute to <button> and <a> elements. The `interesttarget` attribute adds "interest" behaviors to the element, such that when the user "shows interest" in the element, actions are triggered on the target element. Actions can include things like showing a popover. The user agent will handle detecting when the user "shows interest" in the element, via methods such as hovering the element with a mouse, hitting special hotkeys on the keyboard, or long-pressing the element on touchscreens. When interest is shown or lost, an `InterestEvent` will be fired on the target, which have default actions in the case of popovers - showing and hiding the popover. Blink componentBlink>DOM <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/1058 TAG review statusPending Origin Trial NameThe interesttarget Attribute Chromium Trial NameHTMLInterestTargetAttribute Origin Trial documentation link https://open-ui.org/components/interest-invokers.explainer WebFeature UseCounter namekInterestTarget Risks Interoperability and Compatibility None *Gecko*: No signal ( https://github.com/mozilla/standards-positions/issues/1181) *WebKit*: No signal ( https://github.com/WebKit/standards-positions/issues/464) *Web developers*: Strongly positive ( https://github.com/openui/open-ui/issues?q=label%3Ainterest-invokers%20) *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Goals for experimentation Reason this experiment is being extended Due to the complexity of this API, the shape is still in progress. For example, the keyboard behavior was recently changed from a hot-key to a focus-based interest mechanism, to address developer feedback. Due to the changes and the ongoing development/testing of this API, I'd like to request an extension of 3 more milestones, to M140. Ongoing technical constraints None Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?No Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?No Flag name on about://flagsNone Finch feature nameNone Non-finch justificationNone Requires code in //chrome?False Tracking bughttps://issues.chromium.org/issues/326681249 Estimated milestones Origin trial desktop first 135 Origin trial desktop last 137 Origin trial extension 1 end milestone 140 DevTrial on desktop 133 Origin trial Android first 135 Origin trial Android last 137 DevTrial on Android 133 Origin trial WebView first 135 Origin trial WebView last 137 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/4530756656562176?gate=5185152355139584 Links to previous Intent discussionsIntent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/B7F891EB-32FE-48FD-B54B-E452AD74CC3E%40igalia.com Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDiTCMXnR6D-5XdYiwgV_FMAKE8VM%2Bq-Pyho9KZqoDpSjQ%40mail.gmail.com This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- 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+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhZosgitNVTVqQ%3DzznM0JxiH8d0ZoGBManBaE6ByUJ0%2Bg%40mail.gmail.com.