On Tue, 19 May 2009, João Eiras wrote:
How is this different from making two mutations per mutation event, or
calling postMessage() twice for each invokation of the 'message'
event, or loading two new iframes every time an iframe's 'load' event
fires?
It's quite different because
How is this different from making two mutations per mutation event, or
calling postMessage() twice for each invokation of the 'message' event, or
loading two new iframes every time an iframe's 'load' event fires?
It's quite different because in those cases, the events or actions are all
On Tue, 19 May 2009 00:59:03 +0200, João Eiras jo...@opera.com wrote:
If the user agent has no protection against this, then the user will be
forced to close the whole browser, and not just the webpage that is
misbehaving.
Well, just the Web pages that are same-origin and are misbehaving,
On Tue, 7 Apr 2009, João Eiras wrote:
Please consider a typical webpage, that on first load, opens a database
(using openDatabase) and then creates a read-only transaction to read
data to initialize whatever needs initializing. If it's the first time
the user opens that webpage, the
On Wed, Apr 29, 2009 at 1:30 AM, Ian Hickson i...@hixie.ch wrote:
I've changed it a bit, because it seems UAs are likely to still want a
per-origin limit. But I'm not really sure what to suggest that's more
concrete that the vague handwaving that is there now.
Yeah, I'm not sure how to guard
On Wed, 29 Apr 2009, Adam Barth wrote:
By the way, there is a typo in this sentence:
A mostly arbitrary limit of five megabytes per origin is recommended.
Implementation feedback is welcome and will be used to update this
suggestion in _the_ future.
Thanks, fixed.
--
Ian Hickson
