Closed
Bug 434710
Opened 17 years ago
Closed 17 years ago
Unable to remember preferences for JS cookies loaded from file:/// URIs
Categories
(Firefox :: Settings UI, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 430045
People
(Reporter: daniel.thompson, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5
When viewing pages containing JS cookie manipulation that are loaded using file:/// URIs FF3 (b5) is unable to remember the preferences given with respect to 'Allow', 'Allow for session', 'Block'. This makes dealing with such files very painful.
An example of such a system is http://www.tiddlywiki.com/ (self-modifying single file based wiki).
Reproducible: Always
Steps to Reproduce:
1. cd /home/superman
2. wget http://www.tiddlywiki.com/index.html
3. firefox file:///home/superman/index.html
4. Click Allow when queried regarding accepting the cookie
Actual Results:
Continually asked whenever cookies are manipulated to make the decision from 4. again.
Expected Results:
Never asked again about cookie preference for this file.
This, to some degree, a regression from FF2.
I suspect it is because 'empty' hostnames are differently handled in FF3 (in other words I think the preference I managed to establish in FF2 affected all files loaded via file:///).
I cannot force an 'empty' hostname into the list of accepted cookies using the Cookie Manager.
Bug 209964 appears to be most closely related although this is a long standing issue with the extraction of 'hostnames' from file URIs and, being long standing, is not a regression.
Comment 1•17 years ago
|
||
This looks like a duplicate of bug 430045.
Reporter | ||
Comment 2•17 years ago
|
||
Agreed. Don't know why I never spotted that one...
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•