from bug 51266 When at the "about:" page and I select "do not allow cookies from this site", I'm getting an empty Site value in the Cookie Manager.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
QA Contact: tever → cookieqa
mvl: is this still a problem? do we have an !hostPort.IsEmpty() check in the ::Add code somewhere?
this is half-fixed... we won't get an empty entry anymore, but we still throw the prompt that says the site was successfully added. the fix is to change nsPermissionManager::Add() to throw a failure returncode if the host string is empty, and then add an rv exception check to a few places at http://lxr.mozilla.org/seamonkey/source/extensions/cookie/resources/content/cookieNavigatorOverlay.xul#142
For the menu items, shouldn't we be greying out the menu item? File URL's have several other problems, because of the behavior described in bug 109982 (depending on bug 70871) means that the [un]block menu potentially can be used to spank existing hostname entries in Cookie Sites, as well as creating blank entries in "Stored Cookies". I'll file a bug later (gotta run to the library now), and reference it here.
Summary: Selecting "block images" or "block cookies" when you're not on a site (fx about:) adds empty site value → "[Un]Block cookies" for page w/ no hostname -> empty value
It adds "scheme:about" now. Fixed by bug 209689.
Status: ASSIGNED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
depends of bug w/ patch. VERIFIED: Mozilla 1.6f, Mac OS X about: file: -> downloaded version of: http://www.mozilla.org/quality/networking/testing/cookies/jscookietest.html Also, this new behavior leads to bug 235170.
Status: RESOLVED → VERIFIED
Depends on: 209689
QA Contact: cookieqa → benc
Whiteboard: checklinux checkwin
You need to log in before you can comment on or make changes to this bug.