The Focusgroup feature will facilitate keyboard focus navigation using the keyboard arrow keys among a set of focusable elements.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Test out the current design of the "focugroup" attribute and get feedback from developers to eventually guide spec developement. We are working with the Microsoft FAST team (https://github.com/microsoft/fast) and we expect feedback from them and welcome feedback from the entire web community.
Dev tools error logging is supported for various invalid combinations of focusgroup values in HTML.
Supported on all platforms but requires a keyboard with directional arrows.
No milestones specified
--
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.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CH2PR00MB0826E24348B1DBAFE073D32B9BCF9%40CH2PR00MB0826.namprd00.prod.outlook.com.
|
You don't often get email from yoav...@chromium.org.
Learn why this is important
|
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BY5PR00MB0824558B55F935419A66C29C9BD19%40BY5PR00MB0824.namprd00.prod.outlook.com.
Some more details to clarify; while this did get approval all those years ago, a Chrome origin trial was never run, as we did an Edge OT and got enough feedback there to determine that more changes need to be made to the API.
Now that we have a new implementation to follow the changes in the API shape, we would like to request approval to run an Origin Trial in Chrome 146-149.
Could we get that approval here, or should we request it in a new Intent to Experiment thread?
Since the original Intent to Experiment, significant progress has been made in these areas: