Open Bug 1703633 Opened 8 months ago Updated 8 months ago

warning if caret browsing is enabled

Categories

(Firefox :: Keyboard Navigation, enhancement)

78 Branch
enhancement

Tracking

()

People

(Reporter: klaus, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

Accidentally I must have activated "caret browsing".

Actual results:

I was totally unable to navigate page using keyboard, totally frustrated and prepared to give up on Firefox.... :-) Luckily I googled it first and found cor-el answer on this page https://support.mozilla.org/bm/questions/1250328#answer-1198415

Expected results:

May I suggest that some kind of warning or indicator is visible on the screen when this mode is activated. A new come FF user may be scared of from using FF if they accidentally enters this "caret browsing" mode.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

This has a different reason to be warned about than a11y API access, but would it make sense to use some of the same indicator infrastructure?

Flags: needinfo?(jteh)

(In reply to Henri Sivonen (:hsivonen) from comment #2)

This has a different reason to be warned about than a11y API access, but would it make sense to use some of the same indicator infrastructure?

Interesting idea. The a11y API indicator has been disabled for years and it should probably go away altogether at some point. Arguably, there could be similar privacy concerns for a caret browsing indicator (visually revealing the user's accessibility needs), though I'd guess the risk is much lower for caret browsing than it is for API access.

As to whether any of the same infrastructure could be reused from a technical perspective, I'm not sure. Caret browsing is in a completely different module, but I guess it might be possible to reuse some of the front-end code. I'm completely unfamiliar with that code, so I can't give a good answer without digging a lot deeper.

Flags: needinfo?(jteh)
See Also: → 374292, 194937
Component: DOM: UI Events & Focus Handling → Keyboard Navigation
Product: Core → Firefox

Marking this as New given it is an enhancement and already has a component.

Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.