Support for Webcomponents' CustomElements?
Posted: 2021-11-06, 11:58
Recently I came across a few sites that use a relatively new feature (or toy, lol, as you wish) of Webcomponents' CustomElementRegistry. In example a word count class is added to the paragraph HTML tag.
When a website calls window.customElements (without the useful try…catch of course), Palemoon (29.4.1) displays at the console:
TypeError: window.customElements is undefined
Checking about:config in Palemoon, there is a setting for dom.webcomponents.enabled (defaults to false). Setting this to true just vanishes the TypeError.
This demo https://webkit.org/wp-content/uploads/c ... -demo.html should show a progress bar, instead a “ReferenceError: customElements is not defined” is thrown: custom-element-demo.html:34:1
Since this CustomElements stuff was introduced officically in FF63, is this going to be a backported to Palemoon some day, or is there any fallback in Palemoon?
NB: There might be some useful cases for CustomElements, but i fear it will end up just like most other features – motto: it is new!1! so we have to use it on our new site! Like, so, class coffee_machine extends paragraph_tag… Half of the Javascript forest could be lumbered for the use of HTML5 elements (fade in-out-over, resize images), but Javascript seems modern and blown up…
When a website calls window.customElements (without the useful try…catch of course), Palemoon (29.4.1) displays at the console:
TypeError: window.customElements is undefined
Checking about:config in Palemoon, there is a setting for dom.webcomponents.enabled (defaults to false). Setting this to true just vanishes the TypeError.
This demo https://webkit.org/wp-content/uploads/c ... -demo.html should show a progress bar, instead a “ReferenceError: customElements is not defined” is thrown: custom-element-demo.html:34:1
Since this CustomElements stuff was introduced officically in FF63, is this going to be a backported to Palemoon some day, or is there any fallback in Palemoon?
NB: There might be some useful cases for CustomElements, but i fear it will end up just like most other features – motto: it is new!1! so we have to use it on our new site! Like, so, class coffee_machine extends paragraph_tag… Half of the Javascript forest could be lumbered for the use of HTML5 elements (fade in-out-over, resize images), but Javascript seems modern and blown up…
