@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+cims
+eche|off
+hagen
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+rednode
+snex
+synergy3582
Arch
Danny
Holmes
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest74003
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
Sleepy
T3s|4_
U1F642
Wikk_0_
Wikk__
Zapek
aargh4
ac9f
acetone_
ahiru
ananas
anontor2
calamares
dr4wd3_
duanin2
eyedeekay_
eyedeekay_bnc
leopold
mahlay
makoto
marek
mareki2p_
n2
not_bob_afk
poriori_
profetikla
r00tobo
rapidash
test3847473
uop23ip
urist_
wodencafe2
x74a6
zelgomer
eyedeekay
I have figured out how to fix a 5 year old Mozilla bug from extension space
RN
Oh?
eyedeekay
Minor one but yes, the extension system doesn't define behavior for theme.reset which means that anything that changes the color of your browser window breaks all your themes
eyedeekay
I2PIPB changes the color of your browser window when you're browsing I2P so until about 20 minutes ago it broke every third-party theme
eyedeekay
But I managed to figure out a way to define a sane behavior using only the stuff available to me via the WebExtensions API
eyedeekay
It's slower than if they just fixed it but it works and it finally gives me a way to address the thing everybody hates
eyedeekay
This has been my least-favorite extension bug for like a year and a half
RN
That's prety cool! Glad you banged a hammer on it till it works. ;)