I’m sorry, I’m not often someone to whine about Firefox UI. Usually their changes have been for good actually. BUT! But but but. Proper UI design would require AI features to be disabled if the toggle is disabled. This is both highly silly and very confusing.
If it’s not an opt-IN feature, then it’s malicious, anti-consumer design. Full stop.
The lengths people will go to defend Mozilla are astounding. If Chrome did this, you’d be throwing a fit.
Most features in most software are either opt-out or unremovable, though. It’s clearly not about that to you, it’s about the association with AI
I’m also largely against opt-out in other uses, too. The fact that this is AI only makes it that much worse.
No one’s against a feature being opt-out unless they actively dislike that feature. You’re not going to make a post about the context menu items you don’t use unless you have some political opposition against them.
Nobody complains about the ¤ key on their phone’s English QWERTY keyboard, or the “generate QR code from tab” feature in Firefox that I’m sure you’ve never used. Neither of these features is opt-in, and yet you’re content with them. It’s because you don’t have any political opinions about the features themselves. You don’t actually care about opt-out when the feature doesn’t bother you.
Thanks for telling me what I believe in spite of me laying it out in plain English for you. I was confused for a minute there.
if chrome added a toggle to turn off ai features?
… and it was turned on by default and had misleading language as to what the button actually does, yes.