Comment #49 on issue 2906 by mark.finzel: Cookie expiry code throws away valuable cookies (change to last-accessed) http://code.google.com/p/chromium/issues/detail?id=2906
I do not believe this is fixed. I've also posted this comment under 7538. Here is a scenario to re-produce the issue under the current version: I have another scenario that can make this issue happen consistently, without fail. I would suggest you add this to your troubleshooting process. To test this, you need to have a Chase bank/Credit Card account (www.chase.com). The way it is supposed to work is, whenever you have a new computer/browser, Chase requires you to enter a Validation code the first time. My experience on FireFox and IE is that, once you enter it, Chase remembers this validation code for a very long time (months, at least). On Chrome (my version is 1.0.154.48), the Chase site requires me to Confirm my Identity nearly every time I log-in. I'm not sure if this is a cache or cookie issue, perhaps you can tell me something to look for on my system to check. Again, I'm happy to help in any way I can getting this issue resolved. Let me know what I can do. -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
