&zzz
+R4SAS
+RN_
+T3s|4
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Danny
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
cims
dr4wd3_
dr|z3d
duanin2
hababam
hagen_
leopold
makoto
marek
marek22k
n2
noidea
not_bob_afk2
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
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. ;)