Twitter | Search | |
Patrick Brosset
Engineering Manager 🦊 working on Developer Tools 🛠 during the day, father of 3 boys 👶🏻👦🏼👦🏻 the rest of the time.
3,824
Tweets
295
Following
1,401
Followers
Tweets
Patrick Brosset 4h
Replying to @juan_c_c_q
Nope, that’s Firefox. Sorry I should have clarified
Reply Retweet Like
Patrick Brosset 19h
Replying to @4rontender
No this will be in Firefox, likely 69, when it comes out
Reply Retweet Like
Patrick Brosset 20h
Replying to @ThainBBdL
2, 3 weeks or so I’d say, likely turned off by default at first
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @kumarharsh
You are exactly right. That’s how we’ve designed this.
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @KristerKari
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @SherylHohman
69 we hope
Reply Retweet Like
Patrick Brosset Apr 18
A round of well deserved shoutouts for this: for the inspiration, for the spec, for the design and for the coding. This is still in progress, but we’re shooting for Firefox 69
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @mrkmur
They totally could. There might be a lot of false positives though, when progressive enhancement is used for example. But totally worth exploring
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @mrkmur
Not really, this is designed as a runtime tool that only gives you clues as to what might not have effect on a given selected element. Not an audit tool that tells you all the css that’s unused on your site.
Reply Retweet Like
Patrick Brosset Apr 18
Definitely influenced and inspired by your work. Thanks a lot for this!
Reply Retweet Like
Patrick Brosset Apr 18
This isn’t really the audit type of data though. It’s more of a debugging tool. It may report false positives when media queries or progressive enhancement is involved. But it doesn’t matter for this tool as much as it would for lighthouse
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @TheReincarnator
Yes that’s on the radar too.
Reply Retweet Like
Patrick Brosset Apr 18
Replying to @tvanantwerp
Both really!
Reply Retweet Like
Patrick Brosset Apr 18
I've been involved in DevTools dev for years, and I've both had and heard many good ideas to improve it. It's always a special feeling seeing on of them finally take shape. Latest one to date: detect CSS properties that don't have an effect on the current element. Sneak peek:
Reply Retweet Like
Patrick Brosset retweeted
HJ Chen Apr 14
For all my non-Chinese speaking friends, my unprofessional translation effort of 's inspiring talk at CSSConf China can now be found at: Pull requests for better translations welcome
Reply Retweet Like
Patrick Brosset Apr 17
I did some work in the past on explaining CSS linear-gradients. Feels really good that it proved helpful to for his talk on gradients in react native. Relevant part of his talk: Article:
Reply Retweet Like
Patrick Brosset retweeted
Rachel Andrew Apr 16
I've been playing with an early CSS Grid subgrid build in Firefox. Here are some demos and screenshots. I'm so excited to be able to start teaching this!
Reply Retweet Like
Patrick Brosset Apr 16
Omg, ideas? We’ve had them all by know 🤣 It’s the ones we end up implementing that are the best ones.
Reply Retweet Like
Patrick Brosset Apr 13
J’y serais 1 semaine en avance pour ma part.
Reply Retweet Like
Patrick Brosset retweeted
Firefox DevTools Apr 11
Poll: How often do you lose CSS changes in the Inspector by accidentally refreshing the page or clicking a link? — 😅
Reply Retweet Like