W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: [Bug 11606] New: wanted: awareness of non-persistent web storage

From: Glenn Maynard <glenn@zewt.org>
Date: Sun, 26 Dec 2010 15:02:12 -0500
Message-ID: <AANLkTi=6EtwY_2Gg6XkhgiRkeON_j1WDN_sPNc20wamA@mail.gmail.com>
To: public-webapps@w3.org
This made me wonder about this:

> When support for a feature is disabled (e.g. as an emergency measure to mitigate a security problem, or to aid in development, or for performance reasons), user agents must act as if they had no support for the feature whatsoever, and as if the feature was not mentioned in this specification. For example, if a particular feature is accessed via an attribute in a Web IDL interface, the attribute itself would be omitted from the objects that implement that interface — leaving the attribute on the object but making it return null or throw an exception is insufficient.

vs. this:

4.3
> 1. The user agent may throw a SECURITY_ERR exception instead of returning a Storage object if the request violates a policy decision (e.g. if the user agent is configured to not allow the page to persist data).

If localStorage is disabled due to user configuration, which rule
applies?  The former (remove the feature entirely) is much better for
me as a developer.  I've already had to write code to test putting
data in localStorage and see if it throws an exception, on top of
simply saying "'localStorage' in window".



On Sun, Dec 26, 2010 at 11:58 AM,  <bugzilla@jessica.w3.org> wrote:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11606
>
>           Summary: wanted: awareness of non-persistent web storage
>           Product: WebAppsWG
>           Version: unspecified
>          Platform: All
>        OS/Version: All
>            Status: NEW
>          Severity: enhancement
>          Priority: P2
>         Component: Web Storage (editor: Ian Hickson)
>        AssignedTo: ian@hixie.ch
>        ReportedBy: w3.org@mukesh.agrawals.org
>         QAContact: member-webapi-cvs@w3.org
>                CC: ian@hixie.ch, mike@w3.org, public-webapps@w3.org
>
>
> Both Firefox and Chrome offer users privacy features which will cause Web
> Storage to be non-persistent across browser restart. For example Firefox has a
> "Never remember history" option, and Chrome has a "clear cookies and other data
> when I close my browser" option.
>
> For an application developer, it would be helpful to know when such features
> have been enabled, so that the application can inform the user, assist in
> troubleshooting, or disable features that depend on persistent storage.
>
> --
> Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>
>



-- 
Glenn Maynard
Received on Sunday, 26 December 2010 20:02:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:42 GMT