Open Bug 1682093 Opened 4 years ago Updated 1 year ago

C-O key combination moves cursor backward instead of Return key behavior on Mac OS

Categories

(Core :: DOM: Editor, defect, P3)

Firefox 83
defect

Tracking

()

UNCONFIRMED

People

(Reporter: rnkn, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Typing C-o (holding ctrl and typing the O key) in any text field.

Actual results:

Firefox moves cursor backward one character.

Expected results:

C-o should send the equivalent of the return key (technically "operate-and-get-next").

Summary: C-o incorrectly bound → C-O key combination moves cursor backward instead of Return key behavior on Mac OS

I'm still not sure about the expected behaviour here, I did some investigations to see how this works on other browsers and here are the results:

I accessed https://www.wikipedia.org/ and wrote a text in the search area
Firefox: The cursos is moved backward one character.
Chrome: The cursos is moved backward one character.
Safari: The cursos is moved backward one character and search action for the text introduced was performed.

Assigning "Core: DOM: UI Events & Focus Handling" component so we can get an official response to this.
Thanks.

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

Control-O: Insert a new line after the insertion point.

https://support.apple.com/en-us/HT201236

These are macOS system keyboard shortcuts. Firefox should not obstruct these.

Component: DOM: UI Events & Focus Handling → DOM: Editor
Severity: -- → S3
Priority: -- → P3

I think the cursor is moving backward one character because it is supposed to insert a carriage return first, then move back, effectively an "open line". In a search field this should be like pressing return.

n.b. Although these are macOS system key bindings they of course originate from Emacs, and so should function the same way with the GTK Emacs theme.

You need to log in before you can comment on or make changes to this bug.