I have pushed what I have working up to Github at:
I don’t yet have the controls on the center panel, so it starts up immediately and assumes it is NOT in strict mode. It also does not check for successful completion of twenty tones. I’ll deal with that later. My current problem is with sound. I am using the Web API and everything works fine on my desktop machine running the latest Firefox. It behaves exactly as I would expect it to at this time. Then I tried it on my Lenovo Tab 2A and things were not so good. It played back the first note when it initially starts, but that is the last sound that I get. I know that it registers my taps (sometimes) because it will either go on to the next round, or repeat the same one.
I assumed the problem was only on the tablet, but then I decided to try it on the desktop using Chrome. The results were pretty similar to the tablet. I get about three or four notes played before the sound vanishes. After that I can at least SEE that my mouse presses are registering, but no sound until I reload the page to start over.
I tried the example page from fcc in Chrome on the desktop, and it behaved similarly, the first time. Then it seems to have started working properly, so I don’t know what to make of that. On the tablet, the example plays sound when the computer plays the sequence, but not when I respond. Again, it sometime registers the key press and acknoleges a correct sequence, but does not actually light of the button, or make any sound.
If anyone can make sense out of this I would really appreciate it.
Neither Firefox, nor Chrome seem to behave correctly on the tablet, although the behavior is different for my page than it is for the example. On the desktop, Firefox works great for both my code and the example. Chrome now seems to work for the example, but not my code.