1609518 - Several errors triggered while navigating websites with canvas demos.

Status: RESOLVED WORKSFORME

(Core :: Graphics: CanvasWebGL, defect, P5)

Description

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Build ID: 20200115093807

The following websites are throwing several errors during navigation:

• Open web console
• Go to http://html5doctor.com/demos/video-canvas-magic/demo0.html
• Wait for loading the page, and observe that several errors are triggering in web console.

Errors such as:

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.

-Another page: https://codepen.io/eltonkamami/pen/ECrKd
Errors:

Feature Policy: Skipping unsupported feature name “gyroscope”.
SyntaxError: expected expression, got ','

Expected: Websites do not throw errors during navigation.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Aren't these just problems with those pages and not Firefox?

Comment 2

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

Hi Jeff,

I load pages in Chrome and Edge, and the mentioned errors were not triggered. In Chrome were thrown another ones (only in https://codepen.io/eltonkamami/pen/ECrKd ), such as:

• GET https://srv.buysellads.com/ads/CKYDVK7U.json?callback=superagentCallback1579183731415 net::ERR_BLOCKED_BY_CLIENT

• [Honeybadger] Ignoring cross-domain script error: enable CORS to track these types of errors Arguments(5) ["Script error.", "", 0, 0, null, callee: (...), Symbol(Symbol.iterator): ƒ]

• Uncaught TypeError: Cannot read property 'body' of null

None of these appeared in Firefox.

In Edge browser, none errors were displayed after loading these pages.

Hope this information could help! Regards,

Jerónimo.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

If the user observable behaviour of the webpage is different in Firefox then Chrome and you believe the behaviour difference to be caused the error then you'll need to file bugs in the appropriate components for those errors. The error messages you've posted seem more like website issues than problems in Firefox.

Comment 4

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

Hi,
I checked the pages on Chrome and I was able to reproduce the errors. Since this bug is not related to Firefox, I'll close it as Resolved - Works for me.

Thanks for the advise, regards!

Jerónimo.