&zzz
+R4SAS
+RN_
+Stormycloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy_
Danny
DeltaOreo
FreefallHeavens
Guest99
Irc2PGuest13210
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest27928
Irc2PGuest32330
Irc2PGuest74254
Irc2PGuest76033
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe_
T3s|4_
Teeed
Uncrushed_
aargh2
ac9f_
acetone_
anontor2
b3t4f4c3___
dr4wd3
duanin2
erniee
eyedeekay_bnc
fus3r11
leopold_
makoto
n1
nilbog-
noidea
onon_1
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
x74a6
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. ;)