@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+hk
+lbt
+mad
+orignal
+postman
+segfault
+weko
+wodencafe
An0nm0n
Arch
DeltaOreo
FreefallHeavens
Irc2PGuest25907
Irc2PGuest43241
Irc2PGuest59134
Irc2PGuest67004
Irc2PGuest98994
Irc2PGuest99921
Leopold
Nausicaa
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SoniEx2
T3s|4_
acetone_
anon2
b3t4f4c3__
boonst
carried6590
cumlord
dr4wd3
eyedeekay_bnc
l337s
not_bob_afk
poriori_
profetikla
qend-irc2p
r3med1tz-
radakayot__
rapidash
shiver_1
solidx66
syncthing
u5657_1
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. ;)