Bug 148094

Summary: Include IndexedDB status and will-change support
Product: WebKit Reporter: Jon Davis <jond>
Component: WebCore Misc.Assignee: Jon Davis <jond>
Status: RESOLVED FIXED    
Severity: Normal CC: benjamin, commit-queue, timothy
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Add IndexedDB and will-change entries to status page.
ggaren: review-
Add IndexedDB to the feature status page
none
Add IndexedDB to the feature status page none

Jon Davis
Reported 2015-08-17 14:22:09 PDT
The status page should list IndexedDB status and include the recently added will-change support.
Attachments
Add IndexedDB and will-change entries to status page. (2.96 KB, patch)
2015-08-17 14:27 PDT, Jon Davis 		ggaren: review-
DetailsFormatted DiffDiff
Add IndexedDB to the feature status page (1.28 KB, patch)
2015-08-27 09:57 PDT, Jon Davis 		no flags
DetailsFormatted DiffDiff
Add IndexedDB to the feature status page (1.37 KB, patch)
2015-08-27 10:31 PDT, Jon Davis 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Jon Davis
Comment 1 2015-08-17 14:27:49 PDT
Created attachment 259183 [details] Add IndexedDB and will-change entries to status page.
Geoffrey Garen
Comment 2 2015-08-17 14:31:00 PDT
Comment on attachment 259183 [details] Add IndexedDB and will-change entries to status page. Looks like this patch has a conflict.
Jon Davis
Comment 3 2015-08-27 09:57:14 PDT
Created attachment 260062 [details] Add IndexedDB to the feature status page
Jon Davis
Comment 4 2015-08-27 10:31:25 PDT
Created attachment 260066 [details] Add IndexedDB to the feature status page
WebKit Commit Bot
Comment 5 2015-08-27 14:24:07 PDT
Comment on attachment 260066 [details] Add IndexedDB to the feature status page Clearing flags on attachment: 260066 Committed r189051: <http://trac.webkit.org/changeset/189051>
WebKit Commit Bot
Comment 6 2015-08-27 14:24:10 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.