-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support URLs into records #57
Comments
Now that we have Service Workers and soon - including Foreign Fetch - it's unclear we'd want this, rather than allowing an origin to define its own URL namespace backed by IDB queries. |
I suspect that this would still be quite useful. If for no other reason than that Service Workers won't be installed on the first run. I also know that one of the asks from the Google font people was to have a URL which would either quickly succeed, or quickly fail. Either would result in rendering using some font, which was the most important thing when rendering a page. Another way to look at this is: Will Service Workers make people stop using the filesystem:// URL scheme in chrome? |
FWIW, hacky demo using SWs, to show what's involved |
TPAC 2019 Web Apps Indexed DB triage notes: This is probably better served by service workers and cache API, possibly with static routing to avoid running any user code. |
https://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0081.html
Imported from https://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures
The text was updated successfully, but these errors were encountered: