so as long as you don't close devtools, basically this entire panel will be kept in the memory, as object with data and HTML elements, even switching to other tabs or going to other websites didn't cause CG

i'm fixing a memory leak in firefox devtools. Most of the objects and html elements that are associated with the rules and properties are not garbage collected due to uncareful use of Map() in a singleton, an unremoved event listener creating closure and a LOT of circular references

Here is #firefox #devtools for comparison, you can easily (un)check the properties and navigate straight into them to update them. It's not perfect but it's there

I'm working on some #accessibility features in firefox devtools and i decided to look at what's going on in chrome devtools

My verdict is that it needs some love & care :(

1) The visual indication with 2 outlines is ugly, clearly unintended

Improving #firefox #devtools little by little. This time I fixed chaotic text selection when switching between color formats

While working on keyboard accessibility for another tooltip, I looked at how the color tooltip handles it.

Well... I got it to show the blue outline on the first focusable element when click-opening it, and not show the same outline when using the keyboard

It should be the other way around!

Visited Bluesky HQ (Parque Das Aves - Foz do Iguaçu - Brasil)