aboutsummaryrefslogtreecommitdiff
path: root/html/jspage.pl
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2021-04-07 07:16:01 +0100
committerSimon Tatham <anakin@pobox.com>2021-04-07 07:16:01 +0100
commit245e4f8ab45f6b2f74923a9a7a189f87c5d2152c (patch)
treea9babbb573931eb67d6153226444817e8e02a51a /html/jspage.pl
parent8c97ef434f2003768a509f9a76a2b019a08966cb (diff)
downloadpuzzles-245e4f8ab45f6b2f74923a9a7a189f87c5d2152c.zip
puzzles-245e4f8ab45f6b2f74923a9a7a189f87c5d2152c.tar.gz
puzzles-245e4f8ab45f6b2f74923a9a7a189f87c5d2152c.tar.bz2
puzzles-245e4f8ab45f6b2f74923a9a7a189f87c5d2152c.tar.xz
Reword the apology when web puzzles fail to load.
The old one was totally out of date (it mentioned typed arrays and a specific set of browser versions against which the previous Emscripten build had been tested). Also, a couple of users in the last day or two have reported mysterious failures of the WASM puzzles, which I haven't been able to reproduce in the same version of the same browser. So something odd is going on, and this seems like a good place to put suggestions about what diagnostic information to send.
Diffstat (limited to 'html/jspage.pl')
-rwxr-xr-xhtml/jspage.pl18
1 files changed, 12 insertions, 6 deletions
diff --git a/html/jspage.pl b/html/jspage.pl
index b409783..599295b 100755
--- a/html/jspage.pl
+++ b/html/jspage.pl
@@ -245,12 +245,18 @@ ${unfinishedpara}
</div>
</div>
<div id="apology">
-Sorry, this Javascript puzzle doesn't seem to work in your web
-browser. Perhaps you have Javascript disabled, or perhaps your browser
-doesn't provide a feature that the puzzle code requires (such as
-<a href="https://developer.mozilla.org/en-US/docs/JavaScript/Typed_arrays">typed arrays</a>).
-These puzzles have been successfully run in Firefox 19, Chrome 26,
-Internet Explorer 10 and Safari 6.
+<p>Sorry, this WebAssembly puzzle doesn't seem to work in your web
+browser.</p>
+<p>Most modern browsers should support WASM, but if yours isn't
+working, please report the problem, including <strong>as much
+diagnostic information as you can find</strong>.</p>
+<p>In particular, try opening your browser's Javascript error console
+and then reloading this page, and tell me if it reports any error
+messages.</p>
+<p>Also, if your browser has a network diagnostic tab, try the same
+experiment, to make sure it is successfully loading both of the
+auxiliary files <code>${filename}.js</code> and
+<code>${filename}.wasm</code>.</p>
</div>
<hr>