Updates:
Owner: [email protected]
Cc: [email protected]
Labels: -Pri-1 Pri-2 Evangelism
Comment #6 on issue 22181 by [email protected]: Can't log in to CNET
w/Chrome
http://code.google.com/p/chromium/issues/detail?id=22181
They are trying to detect whether the browser supports HTML5 localStorage
and if so, use it
instead of cookies. However, they are doing in the way we have't thought
about:
var supportsSessionStorage = (typeof Storage != "undefined");
We return true, since window.Storage returns a valid constructor. However,
we actually
don't support storage -- and attempt to communicate this by returning null
when querying
window.sessionStorage.
This is a head-scratcher, because it would be very hard to switch
availability of
window.[constructor] members at runtime.
However, the good news the problem will go away once Jeremy is done with
implementing HTML5
Storage API.
So I would suggest approaching it in two ways:
1) contact CNET and ask them to change their detection to:
var supportsSessionStorage = !!window.sessionStorage;
2) cheer for Jeremy wildly and insistently until he finishes his work.
But I doubt this is a P1.
--
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
-~----------~----~----~----~------~----~------~--~---
