HTML5 related problem

[ben557]

This is my friend's portfolio:

https://ryanspice.com/R6.1/

It fully works on all browsers except Pale Moon. Though it works in Firefox, it's slow -- but it does work!

[Moonchild]

I'd say it's a bug on the website.
See the large amount of errors in markup:
http://validator.w3.org/check?uri=https ... ne&group=0

Firefox might be able to guess a few more incorrect things correctly, but I'd suggest that your friend goes in and tries to make the website at least somewhat standards compliant to make it more accessible to the public, especially if it's a portfolio.

[ben557]

Yeah, I bug him about being lazy quite often. I even told him a few weeks ago how to irradicate the note: "* Old GameMaker files don't support Vista or Up" using a utility designed to upgrade Game Maker executables, and he still hasn't updated them.

[ben557]

none of them, have anything to do with the canvas element or why it doesnt work in palemoon, its all HTML validation. the canvas doesn't display because of:

[19:32:30.232] Error: useless setTimeout call (missing quotes around argument?) @ https://ryanspice.com/R6.1/js/spice.js:2385
which you find in the javascript console, this breaks program thus preventing certain alignments actions to be had.

additionally this error:

[19:32:19.003] 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. @ http://start.palemoon.org/https://ryanspice.com/R6.1/

maybe of use when considering that I don't declare a doc type.

However, what is stopping the program from running is most likely due to the syntax used for the game loop found in the first error. What I can tell you is that the program is failing to find a requestAnimationFrame or similar. The fallback is a setTimeout call. This is where the program fails.

[Moonchild]

requestAnimationFrame() is fully supported in Pale Moon.

So in that case the problem is twofold in the js library in use: incorrect feature detection, and a broken fallback routine due to a syntax error.

Edit: a quick look in spice.js shows it's riddled with userAgent detection/matching, including the polyfill used for requestAnimationFrame() at the very end. Do not use userAgent sniffing. It's a bad idea.