-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Doesn't work with Angular 6 when built with production mode #77
Comments
@steven-hyde @chakib-mohamed Does this not require a JavaScript option? I opened up the stackblitz and see :root. Still learning this myself, to be honest. If you guys figured this out only using css I would love to see your approach. |
@chakib-mohamed, @steven-hyde, @winnemucca -- Apologies for the delayed response. I was focused on other tasks for a few months, but I am now trying to catch up on GitHub issues. I make no claims of being an Angular expert so perhaps I'm missing something, but I was able to put together a demo of the ponyfill working with Angular 6 in production mode on StackBlitz: Setup was pretty simple once the basic Angular app was in place:
Tested in IE by loading the preview window only (https://css-vars-ponyfill-77.stackblitz.io/). Works as expected, with ponyfill-processed CSS available in the console. Happy to help investigate further if needed, but as I mentioned my Angular skills are limited. |
@chakib-mohamed, @steven-hyde, @winnemucca -- Since I have not heard back, I am going to assume this issue has been resolved. I am happy to investigate further if you are able to provide additional information that allows me to reproduce the error. |
We were having the exact same issue - everything working fine on localhost, but after deployment components that were not encapsulated were not being properly styled in IE11. We managed to get around the issue by setting the |
Hello,
It seems that the example provided in : https://stackblitz.com/edit/css-vars-ponyfill-29 dosn't work in IE11 when i start the application with production mode enabled : ng serve --prod
Do you have any idea of the origin of the problem ?
Thanks in advance.
The text was updated successfully, but these errors were encountered: