I think part of it is that polymer folks rely a lot on non-standard extensions and say "Things look great from here!"
-
-
I brought up theming years ago and the situation is still pretty meh (at best) for standard WCs.
1 reply 0 retweets 1 like -
custom properties, calc, variables, etc certainly help but we need a full solution for theming worked out.
2 replies 0 retweets 3 likes -
Replying to @wycats
I think custom props and at-apply are solid but at-apply has no implementation progress yet so yeah not very usable right now :/
3 replies 0 retweets 2 likes -
at-apply has no clear spec, that's a first problem. A second problem is that we need list-valued properties for it to work.
1 reply 0 retweets 1 like -
Replying to @FremyCompany @domenic
w/o something in the ballpark of at-apply, we can't even get off the ground on theming. Focus on theming is needed
1 reply 0 retweets 0 likes -
Not entirely true. You can achieve the same thing without at-apply if you ask a preprocessor for help.
2 replies 0 retweets 0 likes -
Replying to @FremyCompany @domenic
right. You can add stuff on top but then ppl looking at the spec go
1 reply 0 retweets 0 likes -
especially since the argument is that we standardize as a community around the spec to reduce "special snowflake"!
1 reply 0 retweets 0 likes -
you can literally use at-apply and have a preprocessor make it work for u; i'd call that an ok polyfill while we get there
1 reply 0 retweets 1 like
maybe what we need is tracked process towards goals rather than techs. "can we theme yet?" "can we self-host yet?"
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.