-
Notifications
You must be signed in to change notification settings - Fork 44
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
custom-style causing issues with @angular2-material library #64
Comments
Can't see any workarounds – this function should probably be refined a bit to create |
I have been seeing issues with material2 styles and it looks like this is the culprit. It's unfortunate that this is still sitting here unassigned :( @Saulis Do you know how to detect if the css "has Polymer css mixins or properties present"? I'm guessing that this would need something more than just looking for We've had to re-declare our material2 styles inside of Angular components to get them to work again. It's pretty ugly. |
Actually, I debugged my issues further and with or without the |
@Splaktar can you share some details on how you configured material theming system to get it to work with polymer? Would be very helpful. |
The same issue for me. Can you please describe how to solve it? |
@jaichandra @logvi you can see the repo here and I have a blog post about upgrading from Angular 2 RC.4 and getting this working again here. |
@Splaktar Hm, it doesn't help me :(. I added custom theme but styles still overwritten by |
@logvi the styles aren't overwritten, they just get the |
In apps which already use @angular2-material library, using polymer elements with angular2-polymer breaks material library css styles.
below line is causing issue:
Because the above code uses
prototype
and overrides the defaultcreateStyleElement
function, it causes all styles to be converted to<style is="custom=style">
tags, thus breaking existing material library styles. Is there a work around for this?The text was updated successfully, but these errors were encountered: