Closed Bug 2084616 Opened 28 days ago Closed 15 days ago

Tab from subject line jumps to UI element, requiring extra tab to type in compose body

Categories

(Thunderbird :: Message Compose Window, defect)

Thunderbird 159
defect

Tracking

(thunderbird_esr153 unaffected, thunderbird158 unaffected, thunderbird159 wontfix, thunderbird160? fixed)

RESOLVED FIXED
161 Branch
Tracking Status
thunderbird_esr153 --- unaffected
thunderbird158 --- unaffected
thunderbird159 --- wontfix
thunderbird160 ? fixed

People

(Reporter: quadronom, Assigned: welpy-cw)

References

(Regression)

Details

(Keywords: access, regression)

Attachments

(1 file, 1 external file)

Attached image screenshot —

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

Steps to reproduce

On tabbing out of the subject line in the compose window instead of bringing the cursor to the editor like it was before now suddenly an UI element (line demarcating top and editor) gets highlighted.

Actual results

N/A

Expected results

The user should land in the editor.

Confirmed

Status: UNCONFIRMED → NEW
Ever confirmed: true

Noticed this too. That's quite annoying, I can't think it's intended.

Flags: needinfo?(arschmitz)
Duplicate of this bug: 2078061
See Also: 2078061 →

It may not be obvious to the average user that an extra tab is the only way to get out of this.
Is it only on mac?

Severity: S4 → S3
Summary: Tab from subject line jumps to UI element → Tab from subject line jumps to UI element, requiring extra tab to type in compose body

No, I get it on linux as well. Would assume all platforms.

Duplicate of this bug: 2087243
Duplicate of this bug: 2087313

This was mentioned on a thunderbird mailing list, mainly for users of screen readers. I think that it's possible that the separator being in the tab order is intentional. Sighted mouse users can drag the horizontal line which is the top of the message body area so as to provide more or less space for the message headers, depending on how many they normally use. So providing a separator in the tab order which can be moved using up/down arrow keys, provides a way for sighted keyboard uses to access this functionality. Similar reasoning also applies to the two focusable separators in the main window.

The problem that this creates is that everyone else expects the tab order to be top down to the next obvious text field, the double-line doesn't give any info, hence it looks like a bug. You can however using the up and down arrows make the icon bar larger or smaller, which doesn't seem to achieve anything useful..

Worse still, its change of behaviour for people that are keyboard based, it didn't used to work like this, so I naturally start typing and expect text, but I get nothing and no obvious reason why, hence the bug report.

Rather than breaking this for all users, how about having it as an accessibility option for those that want it ?
Currently, its very frustrating as your muscle memory expects it work like the last 50 versions have and how virtually every other app works when tabbing around a form.

I agree that it's a problematic solution, assuming that it was the intentional change which I suggested it might be.

Also affects Thunderbird 161.0a1 (2026-10-29) (64-bit).

Agree this "feature" (if it is a feature) should be an accessibility option that can be enabled/disabled as desired.

Keywords: access
Duplicate of this bug: 2087596

I found the discussion interesting and yes it occurs on Win11 25H2 which is my operating system. I hope you all decide on the fix of moving this "feature" into accessibility options. Thank you.

Duplicate of this bug: 2087738
Duplicate of this bug: 2087585

Exclude the compose header splitter from sequential Tab navigation and add
View > Resize Header Area as an alternative keyboard entry point.

Use GTK's keyboard resizing convention: Enter or Space accepts the new
position, while Escape restores the original preferred height, including
automatic layout. This differs from the WAI-ARIA APG window splitter
pattern's suggested Enter behavior, but that pattern has not yet completed
review.

Return focus to the previous control when accepting or cancelling, preserving
the editor caret. Accept changes when focus moves elsewhere, and clean up
session listeners. Disable the command while composing is locked.

Update accessible splitter values after applying layout changes. Verify
focus restoration succeeded and fall back to the editor when the original
control is unavailable or redirects focus.

Cover navigation, resize sessions, held-arrow rollback, keyboard View menu
activation, editor caret preservation, and dynamic skip-tab changes.

Assignee: nobody → h.w.forms
Status: NEW → ASSIGNED

Just to note that there are also focusable separators in other windows which also introduce probably unwanted extra tab stops:
In the main window: After the folder pane (whether or not it is displayed), and before the message pane (whether or not it is displayed).
In the address book window: After the first column, containing the address book tree view.

Blocks: 2088233
Duplicate of this bug: 2088326
No longer blocks: 2088233
Duplicate of this bug: 2088233

See bug 2088233 for accessibility implications .

Duplicate of this bug: 2088361
Duplicate of this bug: 2088435
Target Milestone: --- → 161 Branch

Pushed by daniel@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/36d5c3c694ad
Restore compose Tab navigation with a keyboard header resize command. r=aleca

Status: ASSIGNED → RESOLVED
Closed: 15 days ago
Resolution: --- → FIXED
Duplicate of this bug: 2089691

Uplift to 160?

Flags: needinfo?(arschmitz)

Comment on attachment 9672009 [details]
Bug 2084616 - Restore compose Tab navigation with a keyboard header resize command. r=#thunderbird-front-end-reviewers

Uplift Approval Request

  • Please state case for uplift consideration and ensure bug severity is set: Recent usability regression. Not the most severe issue, but there are already loads of duplicates.
  • User impact if declined: Breaks the workflow of composing a message for apparently lots of users. Also accessibility implications (see bug 2088233)
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Daily?: Yes
  • Has the fix been verified in Beta?: N/A
  • Needs manual test from QA?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Relatively confined front-end change covered by automated tests.
  • Does the fix cause any migrations to be skipped?: No
  • String changes made/needed: New menu item (inside compose window main menu) and aria description (previously missing) of the splitter.
Attachment #9672009 - Flags: approval-comm-release?
Duplicate of this bug: 2089987

Comment on attachment 9672009 [details]
Bug 2084616 - Restore compose Tab navigation with a keyboard header resize command. r=#thunderbird-front-end-reviewers

[Triage Comment]
Approved for release

Attachment #9672009 - Flags: approval-comm-release? → approval-comm-release+
Duplicate of this bug: 2090475
Duplicate of this bug: 2091201
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: