Closed Bug 88187 Opened 24 years ago Closed 23 years ago

[RFE] navigation keys to move focus to invisible recipients in a long list

Categories

(SeaMonkey :: MailNews: Message Display, enhancement, P1)

x86
Windows 2000
enhancement

Tracking

(Not tracked)

VERIFIED WORKSFORME
mozilla1.0

People

(Reporter: michel.poleur, Assigned: ssu0262)

References

Details

(Keywords: access, Whiteboard: [ADT2 RTM])

Attachments

(1 file)

STEPS TO REPRODUCE 1. Compose a new message 2. Enter several recipients until a scrollbar appears 3. Try to move focus to the first recipient you entered (Shift-TAB) RESULTS It's possible to move focus to the first *visible* recipient but not to the first recipient in the list.
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: access
Summary: Need navigation keys to move focus to unvisible recipients in a long list → [RFE] navigation keys to move focus to unvisible recipients in a long list
Severity: enhancement → major
reassigning to varada.
Assignee: sspitzer → varada
Keywords: nsbeta1
Priority: -- → P1
Target Milestone: --- → mozilla0.9.7
Keywords: nsbeta1nsbeta1+
Target Milestone: mozilla0.9.7 → mozilla0.9.9
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.9 → mozilla1.0
reassigning to ssu.
Assignee: varada → ssu
Status: ASSIGNED → NEW
Target Milestone: mozilla1.0 → mozilla0.9.9
Status: NEW → ASSIGNED
Depends on: 124310
Attached patch patch v1.0Splinter Review
Comment on attachment 68916 [details] [diff] [review] patch v1.0 r=bhuvan. As far as autocomplete changes concerned, I think you certainly need to get reviews/approvals to make sure that your changes are in line with their design and has no regressions. Adding Hewitt, Blake to the cc list. Please any other engineers who are well versed with this code.
Attachment #68916 - Flags: review+
Target Milestone: mozilla0.9.9 → mozilla1.0
I'd prefer having to add the property disableMenuPopupViaUpDownKeys if possible, and I think it is possible. What we need to do is add a capturing keypress handler that cancels the event bubbling if the up/down key is pressed.
> I'd prefer having to add the property disableMenuPopupViaUpDownKeys if > possible, and I think it is possible. I don't quite follow. The patch does have the a new disableMenuPopupViaUpDownKeys property. > What we need to do is add a capturing keypress > handler that cancels the event bubbling if the up/down key is pressed. I don't know if that is exactly what is needed because we are still in need to arrow up/down the autocomplete popup list (when shown) as well as ignore the arrow up/down when the autocomplete popup list is not shown. What I mean is that I thought this was all part of the same event. Woudln't preventing the event from bubbling up kill the former?
Whiteboard: [ADT2]
Summary: [RFE] navigation keys to move focus to unvisible recipients in a long list → [RFE] navigation keys to move focus to invisible recipients in a long list
Discussed at mail news bug meeting. Decided to RTM this bug, but we think it might be fixed already. Is this bug fixed?
Whiteboard: [ADT2] → [ADT2 RTM]
this worksforme using the PR1 build which is almost identical to RC2.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
This has been working for months now, verified.
Status: RESOLVED → VERIFIED
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: major → enhancement
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: