On Mon, 6 Aug 2012, Ian Melven wrote:
the spec at
http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#sandboxed-origin-browsing-context-flag
says :
This flag also prevents script from reading from or writing to the
document.cookie IDL attribute, and blocks
On Mon, 6 Aug 2012, Ian Melven wrote:
Adom wrote:
Yes. I think this is actually a consequence of having a unique origin
and doesn't need to be stated explicitly in the spec. (Although we
might want to state it explicitly for the avoidance of doubt.)
yeah, i can see how this situation
Hi,
the spec at
http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#sandboxed-origin-browsing-context-flag
says :
This flag also prevents script from reading from or writing to the
document.cookie IDL attribute, and blocks access to localStorage.
it seems that indexedDB
On Mon, Aug 6, 2012 at 5:08 PM, Ian Melven imel...@mozilla.com wrote:
the spec at
http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#sandboxed-origin-browsing-context-flag
says :
This flag also prevents script from reading from or writing to the
document.cookie IDL
Hi,
- Original Message -
From: Adam Barth w...@adambarth.com
To: Ian Melven imel...@mozilla.com
Cc: whatwg@lists.whatwg.org
Sent: Monday, August 6, 2012 5:12:40 PM
Subject: Re: [whatwg] iframe sandbox and indexedDB
Yes. I think this is actually a consequence of having a unique origin
