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

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

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

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.

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)