I think we need to come up with a good story for styling as well - if everything is jammed into shadow dom by default we end up at square 1
-
-
Replying to @sundress @slightlylate and
So need to figure out how theming works and maybe reify that as well?
1 reply 0 retweets 2 likes -
My approach here would be the same: smuggle all the useful contracts out of the built-ins until such time as we can explain all the behavior
2 replies 0 retweets 2 likes -
Replying to @slightlylate @brucel and
I don't think a good styling story currently exists? What good bits are you referring to?
2 replies 0 retweets 0 likes -
Oh, styling isn't great and probably can't be fixed until last. But we can make re-building your own <select>-alike painless.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @sundress and
Fixing styling in the built-ins is always going to be painful until/unless they come with standardized shadow DOM entrypoints.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @brucel and
I'm not concerned about built ins. I want reusable custom elements that don't have the same styling issues as built ins do today.
3 replies 0 retweets 3 likes -
Yep! That's why focusing on excavation is helpful. We can give CE builders more of the tools we reserved to ourselves to-date.
1 reply 0 retweets 1 like -
Replying to @slightlylate @brucel and
Yes! But without a better styling story we will recreate the same problems, right?
1 reply 0 retweets 1 like -
Replying to @sundress @slightlylate and
As in, capabilities are not the whole story, even though they are a big part.
1 reply 0 retweets 4 likes
Think about it as a hill-climb. What bits can we make super easy for CE developers so there's less work for them overall?
-
-
Replying to @slightlylate @brucel and
So you think we're better off not focusing on reusability?
1 reply 0 retweets 0 likes -
Not what I was driving at, sorry. I probably need to write all of this up somewhere.
1 reply 0 retweets 3 likes - 1 more reply
New conversation -
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.