Open mateoperez opened 10 months ago
If the polyfill relies on configuring properties and they are not configurable, I'm not sure there's a solution unless the polyfill implementation can be somehow fundamentally changed to do something else. Not sure it's possible.
Any luck with this other polyfill?
I've tried that one (https://github.com/ungap/custom-elements) and the error is in the same line (when it is trying to use the native defineProperty):
It is trying to change the constructor for the HTMLElementPrototype
.
The error I had with the webcomponentsjs
polyfill was when it was trying to modify the textContent
from any html element.
Description
I'm trying to use the polyfill on a connected TV using an old browser:
User Agent:
And when the polyfill tries to add a get and a set to any html tag it raises an error:
TypeError: Attempting to configurable attribute of unconfigurable property.
Example
This is the code I'm using, only
core-js
andwebcomponents
polyfills.Steps to reproduce
Launch the app.
Expected behavior
No error is thrown
Actual behavior
TypeError: Attempting to configurable attribute of unconfigurable property.
Version
@webcomponents/webcomponentsjs@2.8.0
Browsers affected