With the loss of <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23625#c3> apply-author-styles <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23625#c3> in Chrome 35, I'm seeing a lot of posts regarding broken css <https://groups.google.com/forum/?fromgroups=#!searchin/polymer-dev/$2Fdeep$2F/polymer-dev/lv8JznvOH4s/1mzv5oadRbgJ>. Beyond bootstrap, however, I have a simpler and broader question. Excuse my ignorance, but I wonder how we can efficiently share styles at all across apps without the *applyAuthoStyles* flag assuming that some may use components and others not?
Maybe someone can explain the following logic from the bug report <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23625#c3> to me...? ^ and ^^ are explicit about what they match and give the author of the component control while applyAuthorStyles requires the author to worry about the internal structure of every nested 3rd party component just in case one of them uses applyAuthorStyles. Is there any way to inherit natural styles within a component anymore (without including the css in every component), or do we have to assume that all css has to be prepared for components? applyAuthorStyles at least offered us the option to be defensive in our coding or not. I'm not seeing a choice anymore.. Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/320dc935-a941-41f4-88d0-c0b8f8170468%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
