+R4SAS
+RN_
+T3s|4
+acetone
+mareki2p
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
FreefallHeavens
Irc2PGuest15434
Irc2PGuest16019
Irc2PGuest20377
Irc2PGuest33925
Irc2PGuest35412
Irc2PGuest77921
MatrixBot
NiceBoat
Onn4l7h
Onn4|7h
Over
Romster
Sisyphus
StormyCloud
T3s|4_
Teeed
aargh4
ahiru
ananas
anontor2
b3t4f4c3___
cims
dr4wd3_
duanin2
eche|off
mahlay
makoto
marek
n2_
nilbog
not_bob_afk2
o3d3
poriori
profetikla
r00tobo
rapidash
rednode
sahil
solidx66
stormycloud[m]
sublimia
test3847473
uop23ip
urist_
vivid_reader56
x74a6
zelgomer
zzz
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. ;)