Open Bug 1363935 Opened 8 years ago Updated 3 years ago

Overriding arrow keys breaks Caret Browsing

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

53 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mozilla.org, Unassigned)

Details

(Keywords: access)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170418122848 Steps to reproduce: Enable Caret Browsing (<F7> or Preferences -> Advanced -> Always use the cursor keys to navigate within pages), load a page that overrides arrow keys such as https://www.nytimes.com/2017/05/10/science/trappist-earth-size-planets-orbits-music.html and try to use the arrow keys to navigate the page. Actual results: <Up> and <Down> have no effect, while <Left> and <Right> navigate to other articles (on any NYTimes article page). Expected results: As an accessibility feature, Caret Browsing (including text selection) should take precedence over the site's key bindings.
Component: Untriaged → Keyboard: Navigation
Keywords: access
Product: Firefox → Core
Olli, should we not be allowing navigation events to go to the page in the case of caret browsing?
Flags: needinfo?(bugs)
To be honest, I have no idea :) Caret browsing is, I believe, very rarely used feature. Do other browsers even have such feature? This is mostly accessibility feature. Perhaps a11y folks have some opinion here.
Flags: needinfo?(bugs) → needinfo?(surkov.alexander)
I'd say caret browsing should take over, at least until we have a scenario how to make them to co-exist together (similar to in-chrome and in-content access keys). Cc'ing more a11y folks.
Flags: needinfo?(surkov.alexander)
Priority: -- → P2
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Component: Keyboard: Navigation → User events and focus handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.