Bug 153783 – Modern IDB: Make sure IndexedDB works from file:// url documents by default

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKit2

[Darryl Pogue]

Created attachment 270465 [details]
Test Case to be served from file:///

Calling indexedDB.open from a file:/// URL results in an InvalidAccessError being thrown. With the removal of WebSQL, this means that local applications served via file:/// URLs have no access to data storage beyond localStorage.

The attached test file should print "Success".
In Webkit, it prints "Error: InvalidAccessError".

[Brady Eidson]

(In reply to comment #0)
> Created attachment 270465 [details]
> Test Case to be served from file:///
> 
> Calling indexedDB.open from a file:/// URL results in an InvalidAccessError
> being thrown. 

Yup, WebIDBFactoryBackend::open fails to make a database identifier for the file: opening origin and top origin.

This is because Safari ramps up the (don't)AllowFileAccessFromFileURLs restriction on file: url documents.

> With the removal of WebSQL, this means that local applications
> served via file:/// URLs have no access to data storage beyond localStorage.

WebSQL has most certainly not been removed... works great in my testing, both http and file URLs.

Why do you think WebSQL has been removed?

[Brady Eidson]

(In reply to comment #1)
> (In reply to comment #0)
> > Created attachment 270465 [details]
> > Test Case to be served from file:///
> > 
> > Calling indexedDB.open from a file:/// URL results in an InvalidAccessError
> > being thrown. 
> 
> Yup, WebIDBFactoryBackend::open fails to make a database identifier for the
> file: opening origin and top origin.
> 
> This is because Safari ramps up the (don't)AllowFileAccessFromFileURLs
> restriction on file: url documents.

It's actually the default in WebKit. NM!

[Brady Eidson]

This should work in Safari for devs. Once Modern IDB gets its WK2 support (soon!), we'll make sure it works there by default.

[Darryl Pogue]

(In reply to comment #1)
> (In reply to comment #0) 
> > With the removal of WebSQL, this means that local applications
> > served via file:/// URLs have no access to data storage beyond localStorage.
> 
> WebSQL has most certainly not been removed... works great in my testing,
> both http and file URLs.
> 
> Why do you think WebSQL has been removed?

I believe WebSQL is not available in WKWebView on iOS (regardless of origin)

[Brady Eidson]

(In reply to comment #4)
> (In reply to comment #1)
> > (In reply to comment #0) 
> > > With the removal of WebSQL, this means that local applications
> > > served via file:/// URLs have no access to data storage beyond localStorage.
> > 
> > WebSQL has most certainly not been removed... works great in my testing,
> > both http and file URLs.
> > 
> > Why do you think WebSQL has been removed?
> 
> I believe WebSQL is not available in WKWebView on iOS (regardless of origin)

Aha, nothing in the bug report suggested you were talking iOS!

WebSQL not working in WKWebView on iOS is a completely separate issue and will be resolved separately.

Could you file a separate bug for that? I know we have a radar but piling on the dupe count from bugzilla will help.

[Brady Eidson]

As of https://trac.webkit.org/changeset/203695 this works.

I'll be making API test changes to make sure it continues working.

[Brady Eidson]

Created attachment 284523 [details]
Patch

[WebKit Commit Bot]

Comment on attachment 284523 [details]
Patch

Clearing flags on attachment: 284523

Committed r203700: <http://trac.webkit.org/changeset/203700>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.