- From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
- Date: Mon, 21 Sep 2009 09:45:22 -0700
- To: public-webapps WG <public-webapps@w3.org>
- Message-Id: <4FB3E545-158B-4B3F-B499-A8A5A6D8E3BB@oracle.com>
There was no response to this earlier, so resending it. Please answer the question: > why allow browsers to selectively block out WebDatabase and not > other kinds of storage? Nikunj On Aug 31, 2009, at 11:07 AM, Nikunj R. Mehta wrote: > In WebDatabase: > > The user agent may raise a SECURITY_ERR exception instead of > returning a Database object if the request violates a policy > decision (e.g. if the user agent is configured to not allow the page > to open databases). > > In WebStorage (emphasis mine): > > When a new HTMLDocument is created, the user agent must check to see > if the document's top-level browsing context has allocated a session > storage area for that document's origin. If it has not, a new > storage area for that document's origin must be created. > > When the localStorage attribute is accessed, the user agent must > check to see if it has allocated a local storage area for the origin > of the Document of the Window object on which the method was > invoked. If it has not, a new storage area for that origin must be > created. > > A browser may not allow local storage for a certain origin, just > like it may not allow cookies to be stored. What is the expected > behavior in that case? > > Alternatively, why allow browsers to selectively block out > WebDatabase and not other kinds of storage? > > Nikunj > http://o-micron.blogspot.com > > > Nikunj http://o-micron.blogspot.com
Received on Monday, 21 September 2009 16:48:01 UTC