@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+dr|z3d
+hagen
+lance074
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
AHOH2
Arch
BubbRubb
C341
Daddy_1
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest57893
Irc2PGuest60494
Irc2PGuest82088
Irc2PGuest85022
Onn4l7h
Onn4|7h
SigSegv
Sleepy
SlippyJoe
Teeed
aargh
ardu
b3t4f4c3__
bak83_
cumlord
death
dr4wd3
duanin2
eyedeekay_bnc
idontpee
not_bob_afk
ohThuku1
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_1
solidx66_
thetia
u5657
uop23ip
w8rabbit
wew
wodencafe
x74a6
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. ;)