Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
On GitHub, a collaborator asked to point out bugs to the DarkReader project. I must say that Microsoft Edge on iOS has some extensions and DarkReader is one of them. It works perfectly fine on those two websites with Edge.
@Mattches@kylehickinson just wanted to tag and point out the above reply, especially since James Mudgett just closed out the Github issue opened earlier. Wanting to confirm what’s next if there are any “Brave specific” issues?
I didn’t know that Brave was using DarkReader library. I can also point out that DarkReader works fine with Safari on iOS. Seems like a Brave bug somewhere.
@Saoiray Seeing if shields affect it would be a good start. DarkReader on Brave is also not up to date on the App Store build and was only recently updated in 1.88.x (currently beta, app store on iOS is 1.86.x right now) so its possible that its fixed there already.
Re: Edge/Safari, Safari will be using the actual extension, not 100% sure about Edge. Brave uses the injected version of the dependency, not the full extension so its possible there are some differences.
The problem has been there for a while. I just decided to report it now. Maybe it’s fixed on newer versions, but I doubt it, since it has always been like this in my experience.
I guess Microsoft is hosting some extensions themselves? They have a few, like uBlock Origin Lite, DarkReader, SponsorBlock, etc. Also on Android. Firefox has some on Android too, but not on iOS.
Since the GitHub report has been closed and the bug hasn’t been reported to the DarkReader project, I suppose it will remain unresolved for the foreseeable future.
@ClaudeC well, part of it would be for you to check like Kyle mentioned. Do you notice any difference with Shields down?
Beyond that, not sure if it’s like Kyle had said:
Seeing that, not sure if it would be fixed. It doesn’t seem Kyle or Matt checked to see and give confirmation either way. I personally am too lazy lately and don’t feel like going through the TestFlight process to add the Beta version, but you can try that via https://testflight.apple.com/join/Trcbh1o3 I believe.
Otherwise we wait for that to arrive to the normal version and see if it gets resolved there.
And if this is the issue, I’m not sure what the next step(s) would be.
I’m assuming this is a very niche thing and kind of low priority overall compared to everything else they are working on and trying to fix. I’m not sure about the “for the foreseeable future” part as they did indicate changes coming that might help.
I did just cave and added it. Seems even with Version 1.88 (108) it’s not working. Doesn’t matter if Shields is disabled. So doesn’t seem to be progress there for at least lapresse.ca
I guess I can try to look at what was linked earlier and see if there is a way to submit an issue with the dark reader project for the OP, just in case it is something they need to do at their end. Otherwise at least wanted to follow up that way if it is something more to look at on Braves and that maybe it can be considered here later.
