marcustyphoon

I've just seen a Chrome user mentioning that they couldn't switch from XKit 7's Old Blue to this extension due to it still being on MV2, so adding a comment...

> I guess this has to be version 2.0.0 since it technically has breaking changes (i.e. does not run on the same browsers). Eh... I mean, yeah, I guess so....

True. I was thinking we didn't major XKit Rewritten on browser version bumps, but I forgot the rule that 0.x.x versions count the second digit bumping as a major.

Today I learned: the CSS web standard has [different keywords called `small`/`large` (based only on the user's browser settings) and `smaller`/`larger` (scales the way we're doing it)](https://developer.mozilla.org/en-US/docs/Web/CSS/font-size#values). Neat! Kind of...

This will work in more places/be more resilient to changes: ```css :root { --chrome-ui: rgb(var(--deprecated-accent)); } ``` There are a bunch of colors this technique won't work on, though, such...

That's odd; that would occur if the extension suddenly wasn't given access to its own storage, but I don't see why that would happen. Have you closed and reopened Firefox...

Based on that I would extremely tentatively guess that the other extension had tried to save... too much data or something invalid in a deeply problematic way...? and crashed, overwhelmed,...

We should strongly consider setting the minimum Firefox version to at least 127, in which users [will (it seems)](https://bugzilla.mozilla.org/show_bug.cgi?id=1889402) continue to have the extension work in the background without manually...

> I haven't looked that deeply into the background script story, but I assume from skimming docs that it should be doable without a Chrome branch and a Firefox branch...

Ooh, yep, that's probably a Tumblr bug with the tools they're exposing for extensions to use for stuff like navigation.