Canvas debugging 
https://twitter.com/mrdoob/status/1037995078482944000 …
For Canvas 2D, Firefox or Safari. For WebGL, Microsoft's @SpectorJS is the best 
I can't think of a tip, so how about a Feedback Friday? What's one thing we're doing well, and one thing we could improve? --- @kaycebasques
-
-
-
Thanks. I saw this discussion and noted this tweet already ;)
- 2 more replies
New conversation -
-
-
Everything is perfect. Only thing that bugs me is when using "console.clear()" is displays the message "The console was cleared" in light grey. I want it to fully clear the console, not even the message should stay.
-
Makes sense. That behavior would make it consistent with terminal UX. ---
@kaycebasques
End of conversation
New conversation -
-
-
I'm curious if DevTools ever received a CSS grid inspector like that of FireFox? Overall though, I've really enjoyed all the updates that keep coming out for DevTools. It's a major reason I stick with Chrome.
-
We've got some Grid features. What else would be helpful for us to add?https://developers.google.com/web/updates/2017/08/devtools-release-notes#css-grid-highlighting …
- 1 more reply
New conversation -
-
-
Lower overhead for the performance profiler. We experience ~2x slowdowns when profiling Figma, which makes it hard to understand impact of user issues since we have a 16ms frame budget. The metadata in the profiles is amazing though! Frames boundaries & input events are
-
Super interesting. Can we repro this somehow?
- 1 more reply
New conversation -
-
-
I really love the network throttling tools. Could be improved by expanding on it (throttle only urls that match a pattern/ability to selectively reject requests etc)
-
FWIW while you can't selectively apply throtting, selective request blocking is a thing. :)pic.twitter.com/nFNrzdrvuc
End of conversation
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.