Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Dayton Paul (DaytonP5)
Auto-Owners Insurance

Auto-Owners Insurance
US
DaytonP5 Member since 2013 20 posts
Auto-Owners Insurance
Posted: Nov 29, 2018
Last activity: Sep 4, 2019
Posted: 29 Nov 2018 13:15 EST
Last activity: 4 Sep 2019 0:06 EDT
Closed
Solved

document.registerElement is deprecated

In Chrome version 70.0.3538.110 developer tools shows the following console message:

[Deprecation] document.registerElement is deprecated and will be removed in M73, around March 2019. Please use window.customElements.define instead. See https://www.chromestatus.com/features/4642138092470272 for more details.

I don't know what this is used for but is there any action we should be taking to treat this prior to March 2019? Will it affect anything at all? This appears to be used in out of the box code out of our control.

To see attachments, please log in.
Pega Platform

Accepted Solution

Posted: 6 years ago
Posted: 29 Nov 2018 13:26 EST
Meghan Atkins (MeghanAtkins)
PEGA
Director, Shared User Services Engineering, Insights & Lists
Pegasystems Inc.
US

Hi,

Thanks for bringing this up!

It looks like that specific function is not widely used in the Pega platform (it is mostly used by some 3rd party libraries that we no longer use). The only thing that is of concern is it'sbeing used by pzpega_ui_jstree which is a 3rd party library we use for the Live UI feature.

​We can fix this in the latest version of Pega and also, depending on the severity of usage, we sometimes create pro-active hotfixes to replace the function that is going to be deprecated by the browser.

​For now this looks like nothing to be concerned about but we will try to fix this in our current version of Pega and in our patch releases for Pega 8.1 if feasible.

Thanks,
Meghan

To see attachments, please log in.
Posted: 6 years ago
Posted: 29 Nov 2018 13:32 EST
John Arnold (JohnArnold) Senior Fellow, Software Engineer, Shared User Services Engineering
Pegasystems Inc.
US

A little more "back story" to follow on Meghan's comment. This is Chrome's note that it will be deprecating the "old" Custom Elements 0 standard that has been replaced by the Custom Elements 1 standard. The evolution from Custom Elements 0 to Custom Elements 1 has been on-going for a while. (Chrome included Custom Elements 0 back in Chrome 33.) 

To see attachments, please log in.
Posted: 5 years ago
Posted: 3 Sep 2019 7:26 EDT
Vidyaranjan AV (Vidyaranjan) Senior Online Community Moderator
Pegasystems Inc.
IN

Hi @Steve.Cotton -

Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.

You may also refer this discussion link as a reference in the new thread.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice