Bookmark title editing: Left/Right arrows triggers pinned tab selection (Up/Down) instead of text navigation

[alfiepoleon]

Captchas

• [x] I have read the instructions.
• [x] I have searched existing issues and avoided creating duplicates.
• [x] I am not filing an enhancement request.
• [ ] I have checked that this issue cannot be reproduced on Mozilla Firefox.
• [x] I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.

What happened?

What happened?

When I try to rename a bookmarked URL title in Zen browser, pressing the left or right arrow keys causes the focus to shift to the pinned tab above or below, respectively. Instead of moving the text cursor within the title field, the arrow keys trigger navigation between different pinned tabs.

What did you expect to happen?

I expected the arrow keys to function as text navigation controls, allowing me to move the cursor within the pinned tab title for precise editing, without causing any focus change or navigation to adjacent pinned tabs.

Version

1.10.3b (Firefox 136.0.4) (aarch64

What platform are you seeing the problem on?

macOS - aarch64

What component is this issue related to?

Bookmarks

Relevant log output if applicable

[bitdryvr]

The OP says bookmarked tab, but I see this issue when trying to rename a pinned tab.

[alfiepoleon]

@bitdryvr I think pinned tab is more accurate, let me edit

[dosubot[bot]]

Hi, @alfiepoleon. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• Problem with Zen browser on macOS where arrow keys shift focus to adjacent pinned tabs.
• Expected behavior: arrow keys should move the text cursor within the bookmark title field.
• Occurs on version 1.10.3b (Firefox 136.0.4), related to Bookmarks component.
• You acknowledged the issue after bitdryvr noted it happens during renaming a pinned tab.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the desktop repository by commenting here.
• If no updates are provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

[alfiepoleon]

It is still relevant with version 1.12.5b (Firefox 138.0.3) (aarch64)

[CodingItWrong]

This is still occurring for me on 1.12.5b (Firefox 138.0.3) (aarch64) too

[addvanced]

As @alfiepoleon and @CodingItWrong said, this is still a problem - and a very annoying one.

[alfiepoleon]

Fixed in version 1.12.9b (Firefox 139.0.1) (aarch64)

[CodingItWrong]

The fix works great!