Open Bug 1744151 Opened 4 years ago Updated 4 years ago

Type ahead find conflicts with sites where keyboard input is needed to interact

Categories

(Toolkit :: Find Toolbar, defect, P3)

Product:
Toolkit
Component:
Find Toolbar
Version:
Firefox 94
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: r.loutrel+github, Unassigned)

Details

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

Steps to reproduce:

1/ Activate option "Start search when typing"

2/ Go to https://hubs.mozilla.com/ and enter a room

3/ try to move with q and e as suggested

Actual results:

it starts a search in the page

Expected results:

it should control the character.

I see several options, none preferred:

  • either site black list for the option "Start search when typing" (controlled by the user)
  • detecting that the focus is on a page "catching" the keys and without any text content to search for

Another solution: a small button near the search box allowing to disable the search for the session on the current page?

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Address Bar

Not sure where this belongs, but it looks like some type-ahead-find bugs are in Core :: Find Backend. This might be more of a front-end Product/UX decision though.

Component: Address Bar → Find Backend
Product: Firefox → Core
Summary: hub conflict between movement keys in room and "start search when typing" option → hub conflict between movement keys in room and "start search when typing" option (type ahead find)

The severity field is not set for this bug.
:harry, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(htwyford)
Severity: -- → S4
Flags: needinfo?(htwyford)
Priority: -- → P3
Summary: hub conflict between movement keys in room and "start search when typing" option (type ahead find) → Type ahead find conflicts with sites where keyboard input is needed to interact

I think this is not really a Core issue; whether keystrokes are routed to the Find bar or to the page is more of a front-end issue. Moving to Toolkit::Find Toolbar for consideration.

Component: Find Backend → Find Toolbar
Product: Core → Toolkit
You need to log in before you can comment on or make changes to this bug.