10 ms·
Chrome is a program that I run on my computer. It protects my interests, not the interests of random crappy website developers doing horrible things like hijac
by CydeWeys 9y ago
Chrome is a program that I run on my computer. It protects my interests, not the interests of random crappy website developers doing horrible things like hijacking clipboard events. I'm all for the defaults being whatever is best for me.
The browser is the agent of the user.
- ksk 9y agoHow is breaking websites good for the user?
- UncleMeat 9y agoAdblock is "breaking websites". If a website is doing something crappy, I'd prefer to not have that crappy thing happen than experience the developer's true intent.
- taneq 9y agoAdblock is opt in.
- nashashmi 9y agoAdblock is opt-in. If the browser misbehaves because of an extension, the browser nor website is to be blamed. Chrome cannot decide on a whim that old websites should be broken. It is not how the web moves forward. Take for example Firefox that kept breaking extensions with every update, now they have few compatible extensions.
- comatose 9y agoit's a little reductio ad absurdum but what about defaulting to popup blocking? blink? marquee? It's not the same thing but maybe worth considering when defending web author's intent being ignored.
- robryan 9y agoAt least popup blocking has an opt out if you need it.
- mcv 9y agoExactly, and this issue could and should have been handled in the same way.
- walterstucco 9y ago> what about defaulting to popup blocking? that's a misbehaviour of the browser, not the developers The browsers were designed for viewing a single page at time popup blocking is fixing a browsers misbehaviour, as much as fixing a car that when you hit the brake accelerates
- 013a 9y agoChoosing to use Chrome is also opt-in. Its the same concept. Its not ideal, but it is what it is.
- walterstucco 9y agodevelopers cannot opt-in
- 013a 9y agoThey also can't opt-in to adblock or noscript or me choosing to run Netscape version 4. Developers fundamentally do not get a say on what I choose to run on my system; at best the only control they have is saying "nope we aren't even going to try to run on whatever you've got" but even that isn't a guarantee.
- walterstucco 9y ago> They also can't opt-in to adblock or noscript or me choosing to run Netscape version 4. This is a gross oversimplifcation They also cannot opt-in if you don't have electricity in your house or don't own a computer DOH! This is not a real argument A real argument is obsolescence Of course there's a point when older versions are not supported anymore Here we are talking about future versions breaking compatibility, without a shared consent, without a deprecation roadmap, that need to be supported, in a Chrome specific way, making Chrome the new IE for no real benefits to the user and a vendor lock-in by Google When they users will try a different browser, for whatever reason, they will experience a different web, that for the majority of them being non techy will look like a broken web
- nashashmi 9y agoI believe Chrome on mobile is the default (only?) browser. So it is opt-out, and a very painful opt-out that requires technical knowledge. You ship an experience like that, you end up not only breaking old websites but shift the emphasis on regularly updated websites that work on mobile. That was the intent! But it is not the web we know and love.
- ksk 9y agoI would wager that if asked, a user would prefer that a website continue to work.
- walterstucco 9y ago> Adblock is "breaking websites" because that's what I want it to do.
- baybal2 9y ago>Chrome is a program that I run on my computer. It protects my interests, not the interests of random crappy website developers doing horrible things like hijacking clipboard events. I'm all for the defaults being whatever is best for me. >The browser is the agent of the user. Here I support you, but do you remember that Googlers pressed assertively for hijackable right click, no opt-out history spoofing, and many many many other supremely user hostile features in W3C standards. Out of all broken web novelties, they prefer to unilaterally break ones coming from outside: Declarative right click menu from Mozilla was killed by Chrome. Declarative SMIL animations, same story They added support for HTTP pipelining and killed it just to force people to migrate to their protocol They had working drag and drop on mobile, yet they killed it because "iphone's dnd is broken, so we made ours broke too" They banned few people from bugzilla from insisting on turning off vibrator API from mobile Chrome, yet the moment people started using it for bot detection, they killed it in iframes (denying its use as a hard proof of clickfraud for ad companies) I always told clients that if you have to choose in between having feature A broken on iphone or having it broken every other browser, to chose to break iPhone. Now, I don't know what is right to say there, probably something like "you need to settle on a variant where stuff is broken in a consistent manner across all browser"
- danmaz74 9y ago> between having feature A broken on iphone or having it broken every other browser, to chose to break iPhone In principle, I agree with you. But in reality, the iPhone market is very valuable.
- tree_of_item 9y agoIf the browser was the agent of the user, the user would decide this behavior.
- currysausage 9y agoAdding another preference certainly won’t solve the underlying usability issues.
- will_hughes 9y agoThat's certainly one view of the world. Come work tech support for a company/product with a web-based form that has a password field in it (like a CRM or other administrative system). Now explain to users why we can't stop their browser filling in their password in the field that's asking for the other user's password. I've had situations where I'm configuring a VPN connection on the web interface for a router... then spending 10 minutes head-scratching why the hell it's giving me an invalid PSK message. Oh, because Chrome filled my password into the goddamn wrong field when it wasn't asked to.
- robryk 9y ago> asking for the other user's password What? Why would the other user ever provide their password to this user?
- techdragon 9y agoHow about an Administration interface that allows you to set a password to a known value for the user to use so they can log back into their account. So the helpful support person can now go "Your password is now 'foobar' and you will be asked to pick a new one when you login."
- desas 9y agoThat doesn't sound like a safe way of resetting passwords. You should supply them a token they can use to set their own password. Your employees should not know your users passwords.
- zaarn 9y agoIn a corporation, this is totally okay as long as the reset password is safe or the account is locked from external access until the password has been changed. The employee should of course change their password and that should be enforced policy, the admin shouldn't know user passwords. Tokens work too but it's a bit of an overhead, especially in smaller SMB where the admin is probably just across the corridor or atleast in the same building.
- chris_wot 9y agoSo it's best to autocomplete bits that shouldn't autocomplete? You've got an interesting idea about protection of end user interests...
- walterstucco 9y ago> The browser is the agent of the user. If that's true, the browser should ask me and not assume what i want it to do.
- gcb0 9y agoFirefox would have given you an option. Which someone would have made an extension to control it for each site. In fact, that is exactly what happens there. Now, Google shoves on you their preference (which is a coin-toss to align or not) and you shout that this is protecting your freedom of choice.
- mcv 9y agoBut is it best for you when sites you use don't work properly because the latest update of your browser breaks the standard? I'm all for giving users the power to ignore the standard and disable certain features, but forcing it on users without making it configurable sounds like a really bad idea. A better idea would be to show that yellow bar at the top explaining briefly what the site does and asking whether the user wants to allow that. That keeps the user informed and empowered, rather than subject to the whims of the website and browser makers.
- ysavir 9y agoIn this case, the browser is the agent of those advertising to the user. It's not protecting your interests, it's protecting Google's interests. If it was protecting your interests, it would be a toggleable setting that defaults to normalized behavior.
- dwild 9y agoI don't really use that auto filling thing that much but the few time I did, Chrome asked me if I wanted to use it on that website. Isn't that what you consider a toggleable setting? I chose to use autofill my user account information on that website.
- halr9000 9y ago> It's not protecting your interests, it's protecting Google's interests. But you can always install (or develop) another browser that might do this job better for you. > If it was protecting your interests, it would be a toggleable setting that defaults to normalized behavior. The problem with this view is that the vast majority of end users do not want, and in fact will never know about or use a new setting, and so the when doesn't move forward. This is the opt-in problem that Google is talking about. In politics, an analogy is called public choice theory.
- pas 9y agoUsers don't use thousands of sites. If a site misbehaves and users want autofill on it, they should be able to override autocomplete=off for that site. Google could even make an extension for this to allow users to gather and share a list of sites that behave in a user unfriendly way. But of course, it was much easier to fuck up half of the Web. Public choice and mandates are great for things that require cooperation and agreement against race to the bottom (like tax havens), not against autocomplete fucking off.
- Tyr42 9y ago> If a site misbehaves and users want autofill on it, they should be able to override autocomplete=off for that site. How? What do you imagine?