On Jun/10/2011 3:05 PM, ext Ian Hickson wrote:
On Fri, 10 Jun 2011, Arthur Barstow wrote:
My take on the comments is that most commentors prefer the spec to be
changed as PLH suggested in comment #5:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12111#c5
Hixie - are you willing
On Sat, 11 Jun 2011, Arthur Barstow wrote:
On Jun/10/2011 3:05 PM, ext Ian Hickson wrote:
On Fri, 10 Jun 2011, Arthur Barstow wrote:
My take on the comments is that most commentors prefer the spec to be
changed as PLH suggested in comment #5:
On Sat, Jun 11, 2011 at 4:32 AM, Arthur Barstow art.bars...@nokia.comwrote:
On Jun/10/2011 3:05 PM, ext Ian Hickson wrote:
On Fri, 10 Jun 2011, Arthur Barstow wrote:
My take on the comments is that most commentors prefer the spec to be
changed as PLH suggested in comment #5:
On Sat, Jun 11, 2011 at 12:32 PM, Arthur Barstow art.bars...@nokia.com wrote:
On Jun/10/2011 3:05 PM, ext Ian Hickson wrote:
On Fri, 10 Jun 2011, Arthur Barstow wrote:
My take on the comments is that most commentors prefer the spec to be
changed as PLH suggested in comment #5:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12941
Summary: If I understand what I'm reading correctly, there's an
error at the end of A background number-crunching
worker tutorial. I think you mean postMessage()
instead of
On Fri, Jun 10, 2011 at 5:13 PM, Cameron McCormack c...@mcc.id.au wrote:
Mark Pilgrim:
What about setVersion() with no arguments? I ask because WebKit
currently treats it like setVersion(undefined) and I'm in the
process of fixing it in about 19 places.
That’s the right behaviour.
Huh?? At
On Sat, 11 Jun 2011, James Robinson wrote:
I am speaking only for myself (and not Google, WebKit, or Chromium) but
I feel obligated to point out that localStorage specifies a
fundamentally broken synchronization model that we are not able to fix
due to compatibility concerns. This is
