This is a great extension, but it falls short when using DarkReader.
- This is filter/filter+ mode
It isn't so bad, but keep in mind that it goes stark and blinding white (the backdrop) when switching themes (in your extension).
- The dynamic theme suffers from this same caveat.
- Static mode:
This is horrid, and just as bad in dark mode.
Now, I'm communicating with the developers over at the dark-reader extension and trying to get some way for other devs to exclude elements from these filters. But that might take a while.
In the meantime, one possible solution would be to place the entire UI inside its own fixed-position fullscreen iFrame, one with a semi-transparent background, to keep the theme.
You could bind the keyboard controls both inside and outside the iFrame and use extension messaging to relay control.
I say both inside and outside because forcibly setting focus to an iFrame isn't possible (to my knowledge). However, a user clicking the central part of the reader would set the focus to the iFrame.
"Wouldn't this have the same result since DarkReader can target iFrames too"? No, because you'd make it an extension page, one that for nearly every user, other extensions cannot access.
This would not be feasible for the bookmarklet distribution, but the extension is nicer anyway, wouldn't hurt to add more features :) .
This is a great extension, but it falls short when using DarkReader.
It isn't so bad, but keep in mind that it goes stark and blinding white (the backdrop) when switching themes (in your extension).
This is horrid, and just as bad in dark mode.
Now, I'm communicating with the developers over at the dark-reader extension and trying to get some way for other devs to exclude elements from these filters. But that might take a while.
In the meantime, one possible solution would be to place the entire UI inside its own fixed-position fullscreen iFrame, one with a semi-transparent background, to keep the theme.
You could bind the keyboard controls both inside and outside the iFrame and use extension messaging to relay control.
I say both inside and outside because forcibly setting focus to an iFrame isn't possible (to my knowledge). However, a user clicking the central part of the reader would set the focus to the iFrame.
"Wouldn't this have the same result since DarkReader can target iFrames too"? No, because you'd make it an extension page, one that for nearly every user, other extensions cannot access.
This would not be feasible for the bookmarklet distribution, but the extension is nicer anyway, wouldn't hurt to add more features :) .