Summary: | [IndexedDB] Key range methods belong to the IDBKeyRange interface | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Andrei Popescu <andreip> | ||||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | bulach, dglazkov, jorlow, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Other | ||||||||
OS: | OS X 10.5 | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 42966 | ||||||||
Attachments: |
|
Description
Andrei Popescu
2010-07-27 08:43:27 PDT
Created attachment 62697 [details]
Patch
Attachment 62697 [details] did not build on chromium: Build output: http://queues.webkit.org/results/3621177 Created attachment 62707 [details]
Patch
Comment on attachment 62707 [details]
Patch
WebCore/page/DOMWindow.cpp:487
+ m_idb_key_range = 0;
not user hacker style
WebCore/page/DOMWindow.cpp:715
+
space isn't really necessary...but not super worried about it.
WebCore/page/DOMWindow.h:235
+ IDBKeyRange* iDBKeyRange() const;
Does casing it like this even work?
r=me
Committed r64141: <http://trac.webkit.org/changeset/64141> |