W3C home > Mailing lists > Public > public-html-comments@w3.org > March 2009

Re: [whatwg] Worker and message port feedback

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 23 Mar 2009 12:38:12 +1300
Message-ID: <11e306600903221638u60808a06h9e832af0de11cc90@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: whatwg@whatwg.org, Discussion of E and other capability languages <e-lang@mail.eros-os.org>, Google Caja Discuss <google-caja-discuss@googlegroups.com>, ServerJS <serverjs@googlegroups.com>, public-html-comments@w3.org
On Sun, Mar 22, 2009 at 10:13 AM, Jonas Sicking <jonas@sicking.cc> wrote:

> It's the vendors that have exposed their users to this inconsistency
> that you should ask. Or maybe sites that use document.cookie a lot and
> that have a lot of chrome or IE8 users. Though both of those browsers
> might be too new to have received a lot of feedback regarding this.
> Note that this is only really a problem on sites that modifies
> document.cookie a lot, and where users have multiple tabs open to the
> same site.


And only when long-running scripts read/write cookies over a long period of
time.

And if something does go wrong, it won't be reproducible, so users,
developers and testers will likely treat it as "just a glitch" and ignore
it. You almost certainly won't get a nice bug report "browser allows race
conditions on cookie data".

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Sunday, 22 March 2009 23:38:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 June 2011 00:13:59 GMT