nandi/frq · 1c7cb6d

modified .modal/web/Dockerfile +3 -1 Viewed

@@ -32,7 +32,9 @@ COPY . .
32	32	# and is not worth an install for one call. Inlined means duplicated, so the
33	33	# flags have to be kept in step with that recipe -- `--pwa-strategy=none`
34	34	# below is one of them, and the deployment is the place it matters most,
35		-# being the one people reach for by URL. The core is compiled to
	35	+# being the one people reach for by URL. See that recipe for what it does
	36	+# and what it does not: an already-installed worker is replaced by an empty
	37	+# one rather than removed, and `flutter/web/index.html` removes it. The core is compiled to
36	38	# JavaScript and copied into `flutter/web/` rather than into the output,
37	39	# because `flutter build web` copies that directory into the bundle -- which
38	40	# is what makes the page's `<script src="frq_core.js">` resolve the same

  # and is not worth an install for one call. Inlined means duplicated, so the
  # flags have to be kept in step with that recipe -- `--pwa-strategy=none`
  # below is one of them, and the deployment is the place it matters most,
--# being the one people reach for by URL. The core is compiled to
++# being the one people reach for by URL. See that recipe for what it does
++# and what it does not: an already-installed worker is replaced by an empty
++# one rather than removed, and `flutter/web/index.html` removes it. The core is compiled to
  # JavaScript and copied into `flutter/web/` rather than into the output,
  # because `flutter build web` copies that directory into the bundle -- which
  # is what makes the page's `<script src="frq_core.js">` resolve the same

modified flutter/web/index.html +28 -0 Viewed

@@ -37,6 +37,34 @@
37	37	uses it, which this page needs because freeq's broker will only redirect
38	38	back to loopback or its own origins — and this is neither.
39	39	-->
	40	+ <!--
	41	+ No service worker, and no leftovers of one.
	42	+
	43	+ The bundle is built `--pwa-strategy=none`, so nothing here registers
	44	+ one any more. That settles a new visitor, but not a browser that
	45	+ installed one before: `none` still emits `flutter_service_worker.js` as
	46	+ an empty file, so the old worker is replaced by a no-op rather than
	47	+ removed, and a no-op registration is still a registration.
	48	+
	49	+ This removes it. The app is a window onto a live IRC connection and has
	50	+ no offline worth the name, so nothing is lost with the caches -- and
	51	+ what they cost was a deploy that would not arrive: a new worker waits
	52	+ until every tab on the origin is closed, so reloading went on serving
	53	+ the previous bundle and the cure was clearing the site data by hand.
	54	+ -->
	55	+ <script>
	56	+ if ("serviceWorker" in navigator) {
	57	+ navigator.serviceWorker.getRegistrations()
	58	+ .then(function (rs) { rs.forEach(function (r) { r.unregister(); }); })
	59	+ .catch(function () { /* nothing to undo */ });
	60	+ }
	61	+ if (window.caches && caches.keys) {
	62	+ caches.keys()
	63	+ .then(function (ks) { ks.forEach(function (k) { caches.delete(k); }); })
	64	+ .catch(function () { /* nothing to undo */ });
	65	+ }
	66	+ </script>
	67	+
40	68	<script src="frq_core.js"></script>
41	69	<script src="frq_dpop.js"></script>
42	70	<script src="frq_oauth.js"></script>

      uses it, which this page needs because freeq's broker will only redirect
      back to loopback or its own origins — and this is neither.
    -->
++  <!--
++    No service worker, and no leftovers of one.
++
++    The bundle is built `--pwa-strategy=none`, so nothing here registers
++    one any more. That settles a new visitor, but not a browser that
++    installed one before: `none` still emits `flutter_service_worker.js` as
++    an empty file, so the old worker is replaced by a no-op rather than
++    removed, and a no-op registration is still a registration.
++
++    This removes it. The app is a window onto a live IRC connection and has
++    no offline worth the name, so nothing is lost with the caches -- and
++    what they cost was a deploy that would not arrive: a new worker waits
++    until every tab on the origin is closed, so reloading went on serving
++    the previous bundle and the cure was clearing the site data by hand.
++  -->
++  <script>
++    if ("serviceWorker" in navigator) {
++      navigator.serviceWorker.getRegistrations()
++        .then(function (rs) { rs.forEach(function (r) { r.unregister(); }); })
++        .catch(function () { /* nothing to undo */ });
++    }
++    if (window.caches && caches.keys) {
++      caches.keys()
++        .then(function (ks) { ks.forEach(function (k) { caches.delete(k); }); })
++        .catch(function () { /* nothing to undo */ });
++    }
++  </script>
++
    <script src="frq_core.js"></script>
    <script src="frq_dpop.js"></script>
    <script src="frq_oauth.js"></script>

modified justfile +7 -3 Viewed

@@ -203,9 +203,13 @@ _web-bundle:
203	203	# the only cure was clearing the site data by hand. Twice in one
204	204	# afternoon a fix looked broken because of it.
205	205	#
206		- # It also retires the workers already installed out there: with no
207		- # `flutter_service_worker.js` left to fetch, a browser update check 404s
208		- # and the registration is dropped.
	206	+ # For workers already installed out there it is less immediate than it
	207	+ # looks. `none` still emits `flutter_service_worker.js`, empty -- a 200
	208	+ # of zero bytes rather than a 404 -- so a browser holding the old one
	209	+ # fetches it, sees it changed, and installs the empty worker, which
	210	+ # waits its turn like any other. It has no fetch handler once it takes
	211	+ # over, so nothing is served from a cache after that; and the page
	212	+ # unregisters it outright, which is what `index.html` does.
209	213	#
210	214	# The comment lives out here rather than inside the quoted script below,
211	215	# which is single-quoted -- an apostrophe in there ends the string, and

      # the only cure was clearing the site data by hand. Twice in one
      # afternoon a fix looked broken because of it.
      #
--    # It also retires the workers already installed out there: with no
++    # For workers already installed out there it is less immediate than it
--    # `flutter_service_worker.js` left to fetch, a browser update check 404s
++    # looks. `none` still emits `flutter_service_worker.js`, empty -- a 200
--    # and the registration is dropped.
++    # of zero bytes rather than a 404 -- so a browser holding the old one
++    # fetches it, sees it changed, and installs the empty worker, which
++    # waits its turn like any other. It has no fetch handler once it takes
++    # over, so nothing is served from a cache after that; and the page
++    # unregisters it outright, which is what `index.html` does.
      #
      # The comment lives out here rather than inside the quoted script below,
      # which is single-quoted -- an apostrophe in there ends the string, and

Removing the worker, not replacing it with an empty one