@eyedeekay
&eche|on
&zzz
+Irc2PGuest3601
+R4SAS
+RN
+StormyCloud
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Dann
DeltaOreo
Irc2PGuest27269
Irc2PGuest65801
Irc2PGuest74254
Irc2PGuest79605
Irc2PGuest8345
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4__
Teeed
aargh2
ac9f_
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gelleger1
leopold_
makoto
matean
n1
nilbog
not_bob_afk
null911
poriori
profetikla
r00tobo_BNC
solidx66
thetia
uop23ip
w8rabbit
x74a6
xHarr
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. ;)