-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add W3C standard Custom Elements to /tools/domprops.json #3037
Comments
This is similar to #2343 in that someone needs to put together a Pull Request after running |
props.html does not pick up most of these (Chrome 65) So I presume they will be erased again when someone PRs props.html output I have added them to my uglify-config.json to be sure:
|
alexlamsl
added a commit
to alexlamsl/UglifyJS
that referenced
this issue
Apr 19, 2019
fixes mishoo#2343 fixes mishoo#3037
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
enhancement
Add standard W3C Custom Elements to /tools/domprops.json, so they do not get mangled
"customElements", "define", "observedAttributes", "attributeChangedCallback", "connectedCallback", "isConnected", "disconnectedCallback", "adoptedCallback"
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements
The text was updated successfully, but these errors were encountered: