- From: Ádám Liszkai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 12 Nov 2016 10:15:02 +0000
- To: public-houdini-archive@w3.org
Oh, the ```var()``` makes it a little-bit better 😄 I like to think about the _CSS mixins_ as virtual collections of _rules_ what can be apply to anything. When I build my application I usually add a bunch of exists _Web Components_ and most of the time their author use a different name for the same functionality what I have already customized and in this way I have ridiculously long CSS assigments. The mixins already a weird thing because if you open a bracket you expect the same functionality that any other class or id and they are not, they are just _CSS property_ with multiple rules. They are not reacting to state changes and you have to collect all of the used elements and states to set them. In multiple level of Shadow DOM it does not work because the states not reflected to the outside of the Shadow DOM, you have to go inside the element and add a bunch of new properties or helper classes for able to do it outside and keep you code clean. It's really hard to maintain a large application if your customer want's to change something, you cannot use a simple stylesheet to change everything you have to go and change the elements to do it, and It's seems to the platform has no better way to do it. It would be nice to have the custom properties like the classes or ids with state changes, because it would shrink down the CSS code length significantly which means faster download time, earlier paint. -- GitHub Notification of comment by adamos42 Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/332#issuecomment-260113605 using your GitHub account
Received on Saturday, 12 November 2016 10:15:08 UTC