Closed Bug 289432 Opened 20 years ago Closed 17 years ago

With cookie sheet, 'cmd-.' stops loading the page but 'esc' denies the cookie

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla.2006.jolinwarren, Unassigned)

References

Details

(Keywords: access, polish)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050405 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050405 Camino/0.8+ If the "Allow Cookie" sheet (or modal window) comes up, the 'cmd-.' key combination does not select 'Deny' as expected. Pressing 'cmd-.' with the cookie sheet active actually stops the site in the main window from loading. Pressing 'esc' in this situation selects the 'Deny' button in the cookie sheet. The proper behaviour is that both 'cmd-.' and 'esc' should perform the same function (which I believe should be do select the 'Deny' button in this case). If the user wants to stop the page from loading, they can hit 'cmd-.' a second time after the cookie sheet has gone away. Reproducible: Always Steps to Reproduce: 1. Enable "Ask before accepting each cookie" in the preferences. 2. Go to a website that uses cookies and is NOT in your cookie exceptions list (eg. http://www.rbs.com) 3. When the sheet comes up asking if you want to accept the cookie, press 'cmd-.' Actual Results: The page behind the sheet stopped loading. Expected Results: The 'Deny' button should have been selected.
Targeting for 1.0.
Keywords: polish
Target Milestone: --- → Camino1.0
Status: UNCONFIRMED → NEW
Ever confirmed: true
Perhaps a side effect of this, full keyboard navigation doesn't work on this sheet, either. I.e., you cannot use tab to navigate between buttons.
-> 1.1
Target Milestone: Camino1.0 → Camino1.1
Assignee: mikepinkerton → stridey
QA Contact: general
Assignee: stridey → nobody
Target Milestone: Camino1.1 → Camino1.2
Target Milestone: Camino1.6 → ---
I don't think this is true anymore.
Yes, it appears this bug has been fixed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.