I'm sure I've used the jsspeccy2 demo page before (months ago), and the emulator ran, but now I get two errors in the JS console upon page load:
Timestamp: 01/16/2014 02:50:31 PM
Error: The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.
Source File: http://jsspeccy.zxdemo.org/
Line: 0
The first is more like a warning of course, but it's still probably a good idea to stick in a charset="utf-8". It's the second that is probably causing problems. None of the controls on the page do anything at all -- presumably the onload script crashes on that error before it sets up any callbacks for them.
A quick web search suggests that createJavaScriptNode is something for the Web Audio API. It might make sense to just disable audio, if the browser doesn't support that API. At the same time, I'm using Firefox 26, and I haven't had any noticeable problem with other pages that use the Web Audio API.
EDIT: oh, I just noticed issue #6 . Almost certainly related.
Hello @gasman,
I'm sure I've used the jsspeccy2 demo page before (months ago), and the emulator ran, but now I get two errors in the JS console upon page load:
The first is more like a warning of course, but it's still probably a good idea to stick in a
charset="utf-8"
. It's the second that is probably causing problems. None of the controls on the page do anything at all -- presumably the onload script crashes on that error before it sets up any callbacks for them.A quick web search suggests that
createJavaScriptNode
is something for the Web Audio API. It might make sense to just disable audio, if the browser doesn't support that API. At the same time, I'm using Firefox 26, and I haven't had any noticeable problem with other pages that use the Web Audio API.EDIT: oh, I just noticed issue #6 . Almost certainly related.