Hi, thanks for reporting! That one is really weird. I have no idea how this could affect webgl, but I confirm it's there. This is also to be expected to still not work after disabling globally or on domain from the popup with the current version, because I still apply the CSS3 filter with invert and hue-rotate, I just give it parameters of 0. In the new version (hopefully coming sometime soon) that will be different, enabling you to at least rather conveniently disabling globally/on domain before loading G Maps etc. and also that super stupid bug where prints are pixelated because it doesn't bother to recalculate the pixel buffer for the significantly higher resolution. (Yes, really. That took me a while to figure out. *facepalm*)

Thank You for taking the time to write a review! I'm glad that this get's appreciated when it only started out as a quick idea from websites bothering me... :D
That possibility pretty much joins all other features waiting for the detailed options page scheduled for 2.0. I could implement checkboxes for these with the current setup in the popup, but that would make it almost unusable. I need a nice structured options page for that.
And if you worry that 2.0 is still a long way to go, worry no more, because I don't have much experience with version numbers and am already considering to make 2.0 the very next version, because it will have major changes like the options page, which would be a waste of time to do before the refactoring I really need to do.
So the real question is, when will I allocate my spare time to make v2.0 a thing (besides studies and all other project I want to do)?

First of all thank You for taking the time to write a review!
That problem seems very weird to me, as I cannot replicate this by simply installing Enhancer for YouTube. Also, the behaviour you are describing seems to be the panel failing to communicate with the local storage api provided by the browser. As my extension currently relies on that to save its state across sessions, you need to have it enabled for the extension to work. If you don't know how to test this, press [F12] to open the developer tools, go to the tab Console send me the output of these commands:

!window.localStorage

and

localStorage.setItem(test, 'test'); localStorage.removeItem('test');

This should determine if local storage works as it should.

Thank You for taking your time to write a review. That's some nice thing I though about at the start but already lost track of over development. Added to the TODO list!