Issue 535: Support cookies on file:// http://code.google.com/p/chromium/issues/detail?id=535
Comment #15 by andy.dean: I must not be understanding the reasoning here. My application runs both on-line and off-line, not a very unusual feature for a statistical calculator. It saves language choice and other preferences in a cookie, which works very well in both IE and FF. In Chrome, it fails to save to the cookie, giving no indication of what is happening, so that I have spent days debugging trying to make it work. Now I find that the user should only run Chrome with a special command-line parameter that not one in a thousand would figure out how to insert. Is this really what you want Chrome to do? I wouldn't mind inserting something in my Javascript to allow cookies (how about document.cookie = "my settings"), or limiting what I write to the cookie, but right now, it seems the only option is to tell people never to use Google Chrome to run OpenEpi off-line. This is a real shame because we hope to use Google Gears later on for the very purpose of enhancing off-line use. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
