@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+RN_
+T3s|4
+cumlord
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+robin
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
HowardPlayzOfAdmin
Irc2PGuest14159
Irc2PGuest28800
Irc2PGuest93285
Onn4l7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4_
Teeed
ac9f
acetone__
ardu
b3t4f4c3__
bak83_
coolbuddy799
dr4wd3
dr|z3d
duanin2
duck
eyedeekay_bnc
leopold_
makoto
marek22k
nilbog
nnm--
not_bob_afk
poriori
pory
profetikla
r00tobo_BNC
rapidash
shiver_
thetia
u5657
uop23ip
w8rabbit
x74a6
xHarr
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. ;)