Post

I’m seizing this moment, as I’ve already sent a selection of 10 bugs to our DevTools team for them to look at 😁 Which papercut bugs would you like to see solved? Send me your crbugs and I’ll forward them. No crbug to point to? No worries: you can always file new ones at crbug.com/new 😉

Barry Pollard@tunetheweb.com

The Chrome DevTools team are doing a "papercuts" sprint where they try to address lots of small, irritating bugs and annoyances. Reply with crbug.com links (no bug, no fix—that's the deal!) and will see what we can do. No promises though as some may be features/too big/unclear how to solve.

It can be very very difficult to hover anywhere when a var has even a small compute tree. Mid size tree? 💀💔 Plus it often tanks performance - sometimes have to close the whole tab and open a new one to get back into devtools. It'd be great if it was truncated - even better to opt-in to *computing*

There are multiple tangentially related bugs already filed for it so the etiquette for "dog piling" my stuff on the team didn't feel great... 🤷‍♀️ If you file anything, please do link it so I can observe how you navigate it. plus I rarely use it when I write CSS so it's mostly a concern for my users 😬

If you can file a bug with a self contained HTML file that repros this then this is a great candidate for us to work on! (I work with Bramus and I'm leading the bug fixing DevTools focus 😁)