Remove comments
This commit is contained in:
1 parent
872175153a
commit
057b4be7d7
18 files changed
+66
-1350
No files matched your search
@@ -4,38 +4,14 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<title>World English Bible Updated</title>
|
||||
<!-- Vendored rather than linked from a CDN: sw.js only caches same-origin
|
||||
responses, so a CDN stylesheet would leave the app unstyled offline. -->
|
||||
<link rel="stylesheet" href="css/bootstrap.min.css">
|
||||
<link rel="stylesheet" href="css/app.css">
|
||||
<meta name="theme-color" content="#1a202c">
|
||||
</head>
|
||||
<body class="bg-body-tertiary">
|
||||
|
||||
<!-- Served by server.py in place of any address a browser navigates to while
|
||||
no service worker is controlling this origin: a first visit, a cleared
|
||||
cache, a reload that bypassed the worker.
|
||||
|
||||
The pages on disk are fragments and the shell is a template, and it is the
|
||||
worker that puts them together. So this page has one job: register the
|
||||
worker and reload once it is running, which lands on the real app at the
|
||||
address that was asked for. It is only ever seen once per device.
|
||||
|
||||
There is no fallback for a device that cannot install one. There used to
|
||||
be -- this page loaded the renderer itself and composed the page in the
|
||||
browser -- and it existed for one case: the app served over plain http://
|
||||
from a LAN address, which is not a secure context, so no worker can
|
||||
register. This app is served over TLS, where that case cannot arise, and
|
||||
the fallback was a second way of building every page that nothing
|
||||
exercised. What is left when registration fails is a sentence saying so,
|
||||
because there is nothing honest to show instead. -->
|
||||
|
||||
<main class="boot container py-5 text-center">
|
||||
<div class="spinner-border text-secondary mb-3" role="status" aria-hidden="true"></div>
|
||||
<!-- Empty until there is something to say. This page is on screen for a
|
||||
moment on a first visit and then never again, and a line naming what it
|
||||
is doing is a line nobody needs to read: the spinner already says wait.
|
||||
It is here, and empty, because it is where fail() writes. -->
|
||||
<p id="boot-status" class="text-body-secondary"></p>
|
||||
<noscript><p class="alert alert-warning d-inline-block">This app builds its
|
||||
pages on the device and needs JavaScript.</p></noscript>
|
||||
|
||||
Reference in new issue
Block a user