@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
AnOtterMoose
Arch
BubbRubb
C341
Chrono
Daddy
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest32228
Irc2PGuest43584
Irc2PGuest82088
Irc2PGuest88009
Onn4l7h
Onn4|7h
Over
Sleepy
SlippyJoe
T3s|4_
Teeed
aargh
acetone
aisle1
ardu
b3t4f4c3___
carried6590
crm114
cumlord
death
dr4wd3_
duanin2
duanin2_
eyedeekay_bnc
nilbog-
nnm--
not_bob_afk
ohThuku1
poriori
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
tr
uop23ip
w8rabbit
weko_
wew-
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. ;)