@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest19353
Irc2PGuest22478
Irc2PGuest48042
Irc2PGuest64530
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
hagen_
khb
not_bob_afk
plap
poriori_
profetikla
rapidash
shiver_1
solidx66
tr
u5657
uop23ip
w8rabbit
weko_
x74a6h
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. ;)