Closed Bug 1738269 Opened 3 years ago Closed 2 years ago

keyboard navigation in new Address Book

Categories

(Thunderbird :: Address Book, defect)

defect

Tracking

(thunderbird_esr91 unaffected)

RESOLVED DUPLICATE of bug 1753093
Tracking Status
thunderbird_esr91 --- unaffected

People

(Reporter: valentin, Unassigned)

Details

The new Address Book (new as of 95.0a1) looks nothing short of gorgeous,
and I think we’ll be gaining some advantages in usability as well.

One thing that remains to address, however, is the keyboard navigation.
Off the top of my head, there are two regressions that stood up to me:

  • F6 no longer allows you to quickly switch between the contact list
    (now named cards) and the list of lists (formerly a tree, now named
    books).
  • I couldn’t find a quick way to immediately focus on the search box;
    Ctrl-K is a no-op, as is /, and Ctrl-F opens up the classic web page search
    (which, by the way, is pretty useless in that particular context).

By the way: it’s rather unfortunate that the new search box has the id searchInput,
since that id’s also that of the main window’s search box (which is mapped to
Ctrl-K, incidentally). May I suggest using a different id here, such as addressSearchInput
or abSearchInput?

See also bug 1738281 and bug 1738288.

Summary: Regression: keyboard navigation in new Address Book → keyboard navigation in new Address Book
Whiteboard: [tb-new-addrbook]

(In reply to Valentin Villenave from comment #2)

See also bug 1738281 and bug 1738288.

Flags: needinfo?(bugzilla2007)
Keywords: dupeme
Whiteboard: [tb-new-addrbook]

(In reply to Valentin Villenave from comment #0)

The new Address Book (new as of 95.0a1) looks nothing short of gorgeous,
and I think we’ll be gaining some advantages in usability as well.

Thank you Valentin, and sorry for late reply!

One thing that remains to address, however, is the keyboard navigation.
Off the top of my head, there are two regressions that stood up to me:

  • F6 no longer allows you to quickly switch between the contact list
    (now named cards) and the list of lists (formerly a tree, now named
    books).

One issue per bug - I've filed that as
Bug 1771005 - Restore F6 fast focus ring in new Address Book

  • I couldn’t find a quick way to immediately focus on the search box;

Sure, I had filed this 4 months ago as bug 1751304 - Re-implement a keyboard shortcut for new Address Book's quick search (Ctrl+Shift+K) .

Ctrl-K is a no-op, as is /,

We'd probably want to reserve Ctrl+K for the traditional global search now that AB lives in a tab next to everything else.

and Ctrl-F opens up the classic web page search
(which, by the way, is pretty useless in that particular context).

Much more useful now because contact data are displayed as real HTML. Switch on caret browsing (F7), search for something particular on the page, and it'll take you right there, press ESC to dismiss find bar, then use Shift+cursor to highlight stuff for copying etc. Depending on scenario, probably much easier than tabbing through each and every thing on the page (esp. for those depending on screen readers).

Hi Valentine,

For your interest: Are you aware of the following meta bug which covers keyboard accessibility in the New Address Book?
Bug 1753093 - [meta] Keyboard UX in the New Address Book (shortcuts, accessibility and ux-efficiency workflows)

(In reply to Wayne Mery (:wsmwk) from comment #3)

(In reply to Valentin Villenave from comment #2)

See also bug 1738281 and bug 1738288.

Thanks Wayne for the ping!

  • I have cleared bug 1738281 with my analysis of Bug 1738281 comment 2.
  • Bug 1738288 is currently confirmed and probably relates to some other focus bugs which I had filed around Ctrl+* focus handling in the contacts list.
  • I have cleared this bug with my analysis of Comment 4, and respective bugs filed by me before and now.

So we're done here.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(bugzilla2007) → needinfo?(valentin)
Resolution: --- → DUPLICATE
Keywords: dupeme
Flags: needinfo?(valentin)
You need to log in before you can comment on or make changes to this bug.