

Yes, with the caveat that function keys such as F7 may not be available and so alternative shortcuts might be needed. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? No special DevTools support is required to debug this feature. The feature will initially be behind a runtime flag and disabled by default. The feature is not exposed to the web API layer. Native caret browsing will rely on the same implementation for rendering a caret and moving it aroundĪs already used within editable content in Chromium. Performance should not be significantly impacted. They would continue to work as they do today having the first opportunity to handle the default activation shortcut. Native caret browsing doesn't aim to replace extensions Mozilla Firefox, Microsoft Edge and Internet Explorer already natively support caret browsing.
#Caret browsing meaning install
There are additional barriers for users of all abilities, since they need to find and install an extension and the functionality.Extensions might not be available in "Incognito" tabs, or when a Guest profile is used.Issue 611798: Enterprise users can't install accessibility extensions).


#Caret browsing meaning activation key
Caret browsing mode will be toggled by an activation key (F7), with a confirmation dialog displayed. In caret browsing a moveable cursor is placed on a web page, allowing a user to select and navigate We are proposing the implementation of native caret browsing in Chromium. It is not expected that web developers will need to make changes to their A TAG review is not requested, because the feature is not intended to be introduced as web standards.
