I won’t go into the details (unless requested), but in recent weeks Yahoo1 Mail has become almost impossible to access in Brave. I have to go to Safari, where there is no problem.
I don’t know whether a login issue can be affected by the usual suspect (ad blocker Shield).
Are there one or more other Shields that are likely to be the ones to disable for that specific problem?
Thanks.
Mac OS 10.15.7 (Catalina)
Brave v.1.68.85 Chromium: 126.0.6478.40 (Official Build) beta (x86_64)
@mk7z unfortunately I fear that this may be due to the outdated version of the browser you’re using. I actually just assisted a user who was seeing ads in their Yahoo! mail earlier today and I was able to visit and login without any issue.
My issue is only related to logging in to Yahoo! Mail. Once I’m in (if I get in), everything is normal. I’m not seeing ads in emails. (I am experiencing other performance issues in Brave. I’m monitoring those and to maintain focus I won’t deal with them here.)
The sequence I have to undergo each time I try to log in to Yahoo! Mail is basically the following (screenshots available if desired, one included below), sometimes with slight variations:
After entering my login ID I have to go through several CAPTCHAs.
Even if I clearly get the first CAPTCHA right (whether bicycles, cars, fire hydrants, crosswalks, etc.), others follow, sometimes with ‘try again’, indicating that Yahoo! (or Google) thinks I didn’t get it right.
When Yahoo! finally seems to have decided I’m okay and it looks like I’m finally gong to ‘get in’, it puts the following on-screen:
Note “Try again tomorrow”. Sure. And the “Help” link is just an on-ramp to paid support.
If I start over, I may or may not be successful getting in on the second try. If not, there’s nothing I can do, except go to Safari, where none of the foregoing occurs.
My version of Safari is the one that’s included in Mac OS 10.15.7 (Catalina). I believe it’s actually of earlier vintage than my version of Brave.
(After checking, my version of Brave is slightly more recent than the one indicated in my original post: Version 1.69.168 Chromium: 128.0.6613.138 (Official Build) (x86_64)
@mk7z I was only pointing out the other user’s issue because in order to investigate it I had to log into yahoo! mail and I did so without issue.
If you’re connected to a VPN when you see this issue, that may be the cause at least for the captchas. I would also recommend, if you haven’t already, clearing cache/site data for the site. You might also want to test in a fresh profile.
I would also be interested to know if other Chromium-based browsers (which Safari is not) show the same behavior.
@mattches Thanks. I clear cache/site data daily now and don’t use a VPN.
Switching to another pre-created profile resulted in a tremendous slowdown (lots of spinning beachball, typed characters appearing long after they were typed, non-response to clicks, etc.). However, once I got in to that profile and proceeded to YahooI Mail I did not experience the issues I reported in the original post. Logging in was straightforward, as in Safari, except for an initial long delay following entry of login ID and password that began several weeks before the issues I reported here. Since Yahoo! lacks any real customer service, I’ve “solved” that by just doing something else for a minute or two before coming back to click the button on the final screen prompt to get in.
Regarding any participation in my issues relating to my computer/OS/browser version, I would expect system degradation to be gradual, not occurring all of a sudden after consistent normal performance, but maybe I’m wrong about that. I’m going to the Apple Store tomorrow to have my MBP Pro checked out. So far it’s never failed any testing that’s been done there. I’ll report the results.
If you still want me to try another Chromium browser for comparison, is there one you’d recommend? It appears that many of them now have built-in privacy features and ad blocking. I assume one without those (or that has the least of those added features) would be the best one to try [?]. If Chromium or ungoogled-chromium are usable by non-tech users (like me) maybe one of those?