This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html Multipage: http://www.whatwg.org/C#sandboxCookies Complete: http://www.whatwg.org/c#sandboxCookies Comment: No user agent will implement the storage mutex so this passage does not reflect reality Posted from: 2620:0:1000:fd28:129a:ddff:feb5:9795 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30
No UA? Or no current UA? In particular, last I heard Mozilla was planning on implementing it because they considered the perf implications to be less bad than letting sites corrupt themselves.
We're going to make a decision about this fairly soon.
(I'm leaning towards changing the spec to basically make the storage mutex optional to implement, with a big scary warning about how not implementing it will lead to sites corrupting themselves.)
Checked in as WHATWG revision r6368. Check-in comment: Allow UAs to opt out of the storage mutex and corrupt data instead of being slow. http://html5.org/tools/web-apps-tracker?from=6367&to=6368