User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 If you have a Post Form in a Mail message and Post to an external web page (i.e. one of the web) which sets a cookie, the cookie is not set when Disable Cookies in Mail & Newsgroups is ticked (in Edit/Preferences/Privay & Settings). The cookie is being set from outside of Mail so I don't see why the cookie should be blocked. Also if the Browser isn't open, the Post doesn't work properly either if the above setting is set. (i.e. the Post data doesn't get read by the browser although it is sent -- I checked this using Live HTTP Headers). Reproducible: Always Steps to Reproduce: 1. Create a Post Form in a Mail Message which points to a web server 2. Have the Posted-to page try and set a cookie 3. Go to another page which trys to then read from the cookie Actual Results: Cookie value not set Expected Results: Cookie value should be set and readible
Option location should actually be Edit/Preferences/Privacy & Security/Cookies - I just can't spell :)
when you submit the form, does the response from the site load in the mail pane or in a new browser window? also, i don't see how the post behavior is affected by this pref, so i'll ignore that part :)
Response loads in Browser window (new if one not open or existing if one is open). I don't really see how the POST behaviour is related either but turning the setting off fixed the POST problem too so I guess may still be related (Perhaps if fix one first and then see what happens :) )
ok, then this might be valid... i wonder if the firstURI check is failing here, or perhaps the docshell walking? darin, what's the expected behavior in this case - would you expect the docshell walk to give APP_TYPE_MAIL here?
also, do you have a mail message testcase you can post here?
For what it is worth, when i have a plain-text email with a url to a page that sets a cookie, and i click the link, the "ask before storing a cookie" dialog pops up. That page is opened in a new window.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.