@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+hk
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb1
Danny
DeltaOreo
FreeB
FreefallHeavens_
HowardPlayzOfAdmin
Irc2PGuest22728
Irc2PGuest51104
Irc2PGuest61213
Irc2PGuest7030
Leopold_xmpp_
Onn4l7h
Over1
Sisyphus
Sleepy
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3___
bak83_
cumlord
death
dr4wd3_
duanin2
duck
eyedeekay_bnc
hagen_
makoto
nilbog-
not_bob_afk
ohThuku1_
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
wodencafe2
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. ;)