@eyedeekay
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+altonen
+dr|z3d
+hagen
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
+y2kboy23
Arch
BubbRubb1
Daddy
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest31631
Irc2PGuest41581
Irc2PGuest92548
Irc2PGuest95056
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe_
StormyCloud_
T3s|4_
T3s|4__
Teeed
ardu
b3t4f4c3___
bak83_
boonst
defaultnick
dr4wd3_
eyedeekay_bnc
guest7621
not_bob_afk
not_human_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
uop23ip
w8rabbit
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. ;)