| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
| |
This saves hammering the FS for every front page request
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This basic service worker behaves identically to the existing appcache -
some static scripts and CSS are cached, any HTML offline instead returns
a static HTML page that knows how to show data on stored problems out of
localStorage (stored there when /my/planned was visited online). Inspect
form submissions will be captured and can be synced back when online.
Once feature parity is established, we will then remove appcache, switch
from using localStorage to the cache API, and hopefully move all offline
support into the service worker.
|
| |
|
|
|
| |
Reads information from a theme object if present, and icons from a
theme directory, with fallbacks.
|
| |
|
|
|
|
| |
`params` changed in Catalyst 5.90116 to always include a sole keyword
parameter (ie. with no equals sign) as a key with an undefined value;
the changelog entry is only "improved test cases for query keywork".
|
| |
|
|
|
| |
This can optionally disable appcache for superusers which can be handy
in development.
|
| | |
|
| |
|
|
| |
The interception of 404s etc is too much of an inconvenience.
|
| | |
|
|
|
Use a list to store JavaScript files, so it can be shared
between the HTML footer and the appcache manifest.
|
