Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome breaks the Web

tonsky.me

Post reply on HN
Print view View original

131–140 of 473 posts

Re: Chrome breaks the Web

#131

Post by iainmerrick »

I understand the push from browser vendors to (as they see it) encourage web developers to keep their sites up to date, but it's crazy how little Google and others seem to care about backwards compatibility.

So many websites from 10 or 20 years ago are unusable now -- if they're even still available. That seems to me a bit of a tragedy. It's sad to just write off that entire slice of human history.

Funnily enough, it's the sites that were quick to adopt the hot new HTML and CSS features from 10 years ago, but then were unable to keep updating indefinitely, that were the worst hit. Really old sites using basic HTML and CSS mostly work OK.

Re: Chrome breaks the Web

#133

Post by wereHamster »

KeitIG wrote: post #122
saas_co_de wrote: post #84

Earlier quoted context omitted.

> does assumption on how things "should" be (in a highly subjective way) They claim they are making these decisions based on user data which I have no reason to doubt. > and breaks the web. Breaks crap websites that are broken already from performance and usability perspective. I personally think this is exactly what is needed to make the web better as a whole. Individual developers working for individual companies a…

Talking from the developer point of view here, not the user's: I'm expecting things to be working the same way they are documented in the manual. The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.

What manual are you referring to? HTML5? That's a living standard, it evolves daily.

Re: Chrome breaks the Web

#134

Post by mathias »

> Which means you can’t practically use the new form without feature detection.

That does not follow.

`{ capture: true }` works in both, since it’s an object, and thus truthy.

There’s no need for feature detection in the case you describe.

Sadly, that’s the whole premise of this article.

It’s only a problem if you want `capture: false` combined with other options — since you’d need to pass in an object, that would be truthy in the old implementations expecting a boolean instead. But then again, the additional options wouldn’t be supported in those old implementations either.

I’m confused — what’s the actual use case that’s breaking here?

Re: Chrome breaks the Web

#135

Post by ksk »

Klathmon wrote: post #121
ksk wrote: post #111

Earlier quoted context omitted.

>and for those users in that moment things might be worse, but it is making the web better for significantly more people, What are you basing this on?

I explained this in my first comment, but I'm also basing it on my own testing in february when this came out, as well as from user feedback for years from users of mobile safari which has done this for quite a long time and it has greatly improved the scrolling performance in their browser.

But how does this apply to the majority of users as you suggest? As a user, I'd like the website to keep working. I don't agree with simply breaking working websites via a top-down dictatorial approach.

Re: Chrome breaks the Web

#136

Post by ksk »

saas_co_de wrote: post #120
ksk wrote: post #105

Earlier quoted context omitted.

We all would like to see this "user data" and make up our own mind. Is the whole open source thing just a gimmick for Google? >Individual developers working for individual companies are rarely if ever thinking about the good of their users, except in a very narrow profit motivated sense, and never thinking about the good of the ecosystem as a whole. >Google is also "breaking the web" by not auto playing videos, not a…

> Its interesting that you're calling for a browser to not implement standards The "standards" are created by the browser makers. It is up to them to decide what the standards are by choosing what to implement. For instance, Apple can decide to not allow 3rd party cookies, which "breaks the web" and "doesn't follow standards" but it is also the right thing to do.

If your position is "anyone can do anything" as long as it has some "perceived good" - in your opinion, then okay, that is your position and I have no argument.

Re: Chrome breaks the Web

#137

Post by agnivade »

dhimes wrote: post #114
Santosh83 wrote: post #108

Earlier quoted context omitted.

Wait, Chrome updates erase your stored passwords!!? At least for me they don't. I have 2 passwords stored in Chrome (not a site important enough to go into KeePass), and have been through multiple updates and yet to lose any passwords.

Yeah- it gets rid of them. Linux chrome. It's been doing it for a while apparently. https://superuser.com/questions/926902/google-chrome-loses-d...

Not for me. Linux Chrome user for quite some time. Never has my credentials been wiped out in an update.

Re: Chrome breaks the Web

#138

Post by krainboltgreene »

wereHamster wrote: post #133
KeitIG wrote: post #122

Earlier quoted context omitted.

Talking from the developer point of view here, not the user's: I'm expecting things to be working the same way they are documented in the manual. The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.

What manual are you referring to? HTML5? That's a living standard, it evolves daily.

WHATWG is a living standard, HTML5 is not.

Re: Chrome breaks the Web

#139

Post by edoceo »

wereHamster wrote: post #133
KeitIG wrote: post #122

Earlier quoted context omitted.

Talking from the developer point of view here, not the user's: I'm expecting things to be working the same way they are documented in the manual. The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.

What manual are you referring to? HTML5? That's a living standard, it evolves daily.

Dude, autocomplete=off should just work. Chrome does the WRONG THING. Spec says what to do, living spec says what to do - Chrome does whatever they want. It's BS. It breaks the web.

Then chrome Devs say to use autocomplete=something-stupid to get the specification behaviour of 'off' WTF is that?!

Donate to Firefox.

Chrome is the new IE

Re: Chrome breaks the Web

#140

Post by KeitIG »

wereHamster wrote: post #133
KeitIG wrote: post #122

Earlier quoted context omitted.

Talking from the developer point of view here, not the user's: I'm expecting things to be working the same way they are documented in the manual. The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.

What manual are you referring to? HTML5? That's a living standard, it evolves daily.

MDN? [1] If you want something more official, here is the W3C doc [2]

[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Fo...

[2] https://www.w3.org/wiki/HTML/Elements/input/text

Post reply on HN