Thank you for the heads-up - I've got it!! --- we are sadly dealing with the ever present and growing "Google disease"
- I'll know now not to post issues involving "customElements" going forward.
(as this issue will presumably be dealt with at some point as referenced below) -- so I'll
check-off this topic as "resolved"
pending further (planned)
developments....
What I gather is --- this has been for sometime an ever present and growing issue for the past 2-3+ years (based on various input on the board) and has perhaps been an issue in some manner far longer since in the "Open Letter to Web Developers" (referenced below) there are footnotes going back 7 years....
A few relevant posts suggest (links referenced below) that
at some point Pale Moon will be dealing with these relevant issues along with all the tangential ramifications involving "web compatibility".
viewtopic.php?f=3&t=23624&p=181942#p181942
... we are in the process of implementing the Google "WebComponents" including customElements. This is slated for Milestone 29. In the meantime, you may wish to contact the developers and inform them that despite it almost being true, not all browsers are Chrome.
Posted Jan 15, 2020 - it is understandable if this plan "slated for Milestone 29" has perhaps been
temporarily placed on hold
....
viewtopic.php?f=70&t=26286&p=209638#p209668
,,, "CustomElements" not functional in Pale Moon at this time...
Posted Feb 23, 2021 - "not... at this time" would suggest an ultimate resolution down the pike at some point....
An
Open Letter to Web Developers:
viewtopic.php?f=1&t=24004
".... While it is absolutely true that it is in our direct interest that web developers don't use something we are still working on implementing ourselves..."
Posted Mar 17, 2020 - (based on the above) I'm assuming Pale Moon is "still working on implementing" a resolution to these issues... (at least for the long-term even if its been temporarily de-railed for obvious reasons)
Point is, it would appear (based on comments reference above) the long-term goal is for Pale Moon to get this issue ultimately resolved.... So then, for the present, there's no point in posting problems that involve "CustomElement" errors, I get it!!!
.... (perhaps including this information in the "Web Compatibility Support" board template might be something to consider
)
So on that point above, I first considered it might be a good idea to send this "Open Letter to Web Developers" to this bank (it
certainly is warranted in my opinion) - but then if the plan is to
still to deal with the "Google disease" at some point, might it be better to not bother and wait for Pale Moon to address these issues? (assuming this is still part of the grand plan for Pale Moon). Let me be clear, I'll gladly send this "Open Letter" to the Discover Bank if Pale Moon support is of the opinion it would be a good idea to do so.
-- it goes without saying that it certainly would be nice to have
web developers, seriously, take into account the excellent points discussed in the "Open Letter".