Closed Bug 107560 Opened 23 years ago Closed 22 years ago

Cookie setting confirm dialog has no keyboard shortcuts

Categories

(Core :: Networking: Cookies, defect, P4)

x86
Windows NT
defect

Tracking

()

RESOLVED FIXED
mozilla1.3beta

People

(Reporter: JimCassidy, Assigned: skasinathan)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

When a site attempts to set a cookie, and the "Confirm" dialog is diaplayed
(Saying "The site www.cookiesareevil.com wants to set a cookie.  Do you want to
allow it?"), the Yes and No buttons do not have keyboard shortcuts.

Reproducible: Always
Steps to Reproduce:
1.  Under Preferences | Privacy & Security | Cookies, check "Warn me before
storing a cookie"
2.  Go to a site that attempts to set a cookie (www.slant-six.com, slashdot.org,
etc).
3.  Witness the dialog missing keyboard shortcuts (Oh, the humanity!)

Actual Results:  Dialog missing keyboard shortcuts 

Expected Results:  Dialog has keyboard shortcuts 

I like Ice Cream
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → mozilla1.1
Tab key works fine, but arrow keys should work too (or instead).
Priority: -- → P4
Target Milestone: mozilla1.1alpha → mozilla1.2beta
Target Milestone: mozilla1.2beta → mozilla1.3beta
Just a comment, many dialogs (in Windows apps, at least) also have keyboard
shortcuts to dialog buttons (like alt-y for Yes, alt-n for No, etc.).  That was
my original intent when submitting this bug, although I usually rely on hitting
escape for cancel/no and enter for ok/yes, which works just fine in Mozilla 1.0.
Hitting Y or N alone (i.e. no Tabbing or Alt) would be optimal IMHO.
*** Bug 178653 has been marked as a duplicate of this bug. ***
*** Bug 179240 has been marked as a duplicate of this bug. ***
-> me
Assignee: morse → suresh
Status: ASSIGNED → NEW
this must be fixed by my recent checkin to cookieviewer.xul.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.