@eyedeekay
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+hagen
+hk
+orignal
+postman
+radakayot
+segfault
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest12735
Irc2PGuest26660
Irc2PGuest39486
Irc2PGuest41990
Irc2PGuest59134
Irc2PGuest82989
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
aeiou
ardu
b3t4f4c3__
boonst
carried6590
cumlord
death
dr4wd3_
enoxa
eyedeekay_bnc
not_bob_afk
phil
poriori
profetikla
qend-irc2p
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
weko_
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. ;)