Artem Manushenkov

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

los últimos dias hago un poco de jogging, suprime el hambre bastante bien, gracias a esto me salto la cena

pero no se puede engañar a su cuerpo así, voy a tener un hambre voraz mañana 😅

TIL

DOMTokenList.classList.toggle("class", force) needs `force` to be either === true or === false, otherwise it'll ignore it

Now give us proof that anything else besides corn is grown there 😭

St. Petersburg is within Leningrad Oblast, weird they didn't rename it

If you have any bug reports or improvement suggestions, you can file a ticket under firefox devtools category at bugzilla.mozilla.org, or leave a comment here/dm me

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

4) You can't navigate out of the checkbox into the property that it's meant to toggle. Best case scenario is tabbing into the the sourcefile button ( (index) in my case) and pressing ⬅, in the worst case the focus just jumps into the elements tab after pressing space

2) Pressing Enter doesn't do anything, and pressing space triggers the scroll action, removing the css rule from the view

3) You can't even navigate into a checkbox if you haven't somehow activated it (by hovering over the rule for example), if it's hidden, it's inaccessible

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

I can somewhat relate, but in my culture I'd say it's a manifestation of patriarchy, the very practical example of this is how young men are conditioned into doing military service by the patriarch in the family with similar arguments and motivation

Today I learned that instead of `git reset HEAD~1` you can just write `git reset head~` 😅

I consider all of these features AI (Amazing Improvements)

Public libraries can be such a life saver. I'm staying in a crowded hostel in Moscow with unstable wifi connection, but guess what? There's library with free wifi a couple blocks away

I have a free office room just to myself because there's no one else here, just some babushkas picking up books :)

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

We've got a good-first bug for new contributors to Firefox: bugzilla.mozilla.org/show_bug.cgi...

If you're interested in writing a little bit of C++/HTML/JS to make your first contribution, let me know! I'd be happy to guide you through the whole process over chat or video call.

Filed an improvement request bugzilla.mozilla.org/show_bug.cgi...

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)

Several folks were interested but no one claimed it yet 🤒 I love your enthusiasm though! Would love to work on some bugs adjacent to your sphere of influence after I'm done with a big feature I'm adding to devtools