- cross-posted to:
- technology@lemmy.world
- tech@kbin.social
- technology@beehaw.org
- cross-posted to:
- technology@lemmy.world
- tech@kbin.social
- technology@beehaw.org
Google Chrome will limit ad blockers starting June 2024::The “Manifest V3” rollout is back after letting tensions cool for a year.
deleted by creator
I was doing some work on the social security site and the site i needed wouldn’t even load unless it was chrome or edge. There are sadly too many important website that are somehow allowed to gatekeep browsers. I feel like if their site follows guidelines then there’s no reason they should be restricted from browsers, but here we are.
Platforms I use don’t work reliably with other browsers, online teaching ones to be specific.
Ah, that’s a tough one.
I needed to install Ungoogled Chromium to join lectures, because the remote learning site refused to work in Firefox (wouldn’t be surprised if it was developed against a chrome-specific API)
Pretty much every internal Web application I’ve used in banking, insurance and Govt orgs.
Most of the time the site doesn’t really need chrome, it’s just that’s all they test it with, so they say it’s a requirement.
There’s an addon for Firefox called User-Agent Switcher and Manager that allows you to have Firefox identify itself to websites as chrome (among others), and it often fixes the problem.
I work in IT so I am aware of this. Maybe you’ve not worked in enough places that just build incompatible (cr)apps?
And sure, just go outside our locked down machine policies and install Firefox and unapproved extensions. That will do down well.
Yeah, “most” was probably a bit hyperbolic, especially for internal websites, and I guess it’s no surprise that the sectors you mentioned would be particularly bad for it.
The best place for my little PSA probably wasn’t in response to your post in particular.
Sorry I’m snippy as I have personal stuff going on. You are right in so far as if you have full control of your machine which isn’t the case for the orgs I mentioned.
We can pull FF into our dev environment so I’ve seen these annoying behaviours.
All good; I didn’t think about your comment thoroughly enough before replying, and you had a very valid point! ^^