[Webkit-unassigned] [Bug 53351] New: DOM Storage should not allow its methods to be overridden
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jan 28 16:25:08 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=53351
Summary: DOM Storage should not allow its methods to be
overridden
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: jorlow at chromium.org
DOM Storage should not allow its methods to be overridden.
Per Ian Hickson in "[Web Storage] A couple questions about the storage spec":
> > > If my reading is right (and it is the behavior I see in a couple
> > browsers) this makes me very nervous, because I can do something like:
> > > window.localStorage.setItem("length", "a value we computer");
> > > window.localStorage.setItem("clear", "something that is
> > transparent");
> > > which of course allows:
> > > window.localStorage["length"];
> > > window.localStorage["clear"];
> > > but in the browsers I've looked at, this (of course) also kinda messes up
> > things like:
> > > for (index = 0; index < window.localStorage.length; index++) {
> > > // whatever
> > > }
> > > window.localStorage.clear();
> > > since length is now not a number, and clear isn't a function.
> >
> > Actually length and clear don't get overrideen, because the interface
> > is not defined as [OverrideBuiltins].
>
> Wha? This seems completely different than your answer in this thread:
> http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-June/020349.html
Not sure if I was just wrong then or if the specs changed between my
replies. At this point the spec seems to match implementations though.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list