-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Web Component Support Broken? #17448
Comments
Hi, sounds like you are using native shadow DOM which is only available in Chrome. Looking at the encapsulation of the component in your project, the component is using Can you check if changing this solves the issue? Thanks. |
AWESOME - Changing to |
Hi @fireflysemantics, I'll answer on SO. |
@alan-agius4 Thanks for elaborating on the SO question. I ran into a new problem. This https://stackoverflow.com/questions/61225191/angular-custom-element-input-property-not-initializing |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Angular CLI generates es5 and es2015 production files and chooses which to load. I seems like this change broke the generation of Web Components.
Wrote the issue up with Github repositories for testing here:
https://stackoverflow.com/questions/61168457/fs-gist-js1-error-typeerror-i-createshadowroot-is-not-a-function-on-angular-we
I've tried testing the webcomponent created in a minimal enviornent:
https://github.com/fireflysemantics/fs-gist-minimal
When loaded it produces this error:
The text was updated successfully, but these errors were encountered: