@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+acetone
+dr|z3d
+hk
+lbt
+postman
+weko
+wodencafe
An0nm0n
Arch
Dann
DeltaOreo
FreefallHeavens
GucciferZ_
Irc2PGuest35128
Irc2PGuest59134
Irc2PGuest61987
Irc2PGuest97364
Irc2PGuest99418
Leopold
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SoniEx2
T3s|4_
T3s|4__
anon
b3t4f4c3__
bak83
boonst
carried6590
cumlord
dr4wd3
eyedeekay_bnc
l337s
not_bob_afk
orignal
poriori_
profetikla
qend-irc2p_
r3med1tz-
radakayot_
rapidash
scottpedia
segfault
shiver_
solidx66_
syncthing2
trust
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. ;)