<not sure if serious> Why not use the "Elements" panel for this? Better auto-complete.
-
-
FYI some of the CSS-in-JS solutions tend to break style manipulation via the elements panel.
1 reply 0 retweets 1 like -
How?
1 reply 0 retweets 0 likes -
Not sure how/why, your mate Sunil knows though.
1 reply 0 retweets 0 likes -
the prod mode thing? editing styles in dev tools is disabled in prod mode (for...reasons), but that's never a problem in dev.
1 reply 0 retweets 0 likes -
But not in the Elements panel? Unless we are talking about different things. I'm thinking of the browser built in Elements panel, where I always edit styles.
2 replies 0 retweets 0 likes -
Replying to @brian_d_vaughn @threepointone and
There’s a CSSOM API that a lot of CSS-in-JS libraries use that causes styles to be uneditable in devtools
1 reply 0 retweets 4 likes -
Replying to @sebmck @threepointone and
Interesting. And that has higher priority than inline styles in the Elements panel, huh? Never heard of that.
2 replies 0 retweets 0 likes -
Replying to @brian_d_vaughn @threepointone and
Inline styles have a higher precedence over anything matched against the element. It's just that editing an uneditble style includes having to write out the property manually in http://element.style which is annoying.
1 reply 1 retweet 0 likes -
Replying to @sebmck @threepointone and
Ah, ok so then that's back to what I though originally. I guess I don't consider that annoying. Browser provides pretty good auto completion
1 reply 0 retweets 0 likes
Yeah, especially when we could have an even more powerful dedicated styling extension that was integrated with a CSS-in-JS lib
-
-
Replying to @sebmck @threepointone and
Yeah. I'm not really interested in React DevTools competiting in that space.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
he/him 