@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+cumlord
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Chrono
Daddy
Danny
DeltaOreo
Irc2PGuest25928
Irc2PGuest3689
Irc2PGuest49308
Irc2PGuest60736
Irc2PGuest85653
Irc2PGuest87600
Irc2PGuest96178
Onn4l7h
Over
RG
Sisyphus
Sleepy
SlippyJoe
aargh2
ac9f_
anter666
b3t4f4c3___
bak83
dr4wd3
dr|z3d
duanin2
eyedeekay_bnc
leopold
makoto
nilbog
not_bob_afk
poriori
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
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. ;)