Hacker News Reader

Comment by stephenr | Hacker News Reader

The problem isn't apple or safari. Chrome copied a safari feature poorly, THAT is the problem.

Yes, Chrome's implementation is extremely buggy and is triggered by all sorts of small movements, in addition to providing terrible clues to the user about what is going on.

Safari's implementation is much less painful, is only triggered when I really want it, and provides sufficient visual clues about what's going on.

Chrome's blunder is almost enough for me to switch to Safari, which is saying a lot given my preference for Chrome otherwise.

I use Safari for this reason, and because it took forever for Google to get out a version that wasn't mostly broken on Lion.

I quite like Safari myself, save for the visible tab limit (8 or 9 on my monitor, and have to use the drop down on right hand side to get to other tabs; what year is this?!) and no favicons. Do you or anyone else happen to know of any remedies for those?

A suite of Safari extensions/hacks known as Glims[1] adds favicons to tabs among other things, not sure about allowing more than 8 or 9 tabs though.

[1]: http://machangout.com/

If it happens in ff the same as its reported to work in chrome, then they're both at fault.

Safaris implementation makes it very clear you are going to navigate back a page, and it's very easy for the user to cancel the action.

Gooogle has a broad-based commitment to breaking scrolling, from scroll bar width hacking to having multiple scrollable regions in a web page with invisible separators, to hiding and reflowing page content to cut off everything off-window. Chrome integrates with Google's web apps, to the point that you never know how to navigate a page if you use a gapped in Chrome.

Indeed; I've never really had an issue with this in Safari, but Chrome's version is very easy to trigger.

And yet the Chrome version lets you block the action, while with Safari you can't do anything about it...

You don't need to "do anything about it" in safari, as it works properly.

I use chrome, and I haven't noticed a problem. Is the issue just than it scrolls back too fast, or won't allow horizontal scrolling period?

I turned it off because it was too annoying, but what it was doing at the time was

* I'd scroll something horizontally,

* I'd reach the edge of the page

* Chrome would render the "I'm about to go back a page" arrow

* Nothing I tried would cancel the "Back" action

It's really bad for something like phpMyAdmin that does a lot of things through POST and doesn't support the back button especially well. Accidently triggering back button can wipe out the query you have made.

PHP has been a leader in breaking the web for much longer than Apple or Google.

Overuse of POST should help, though, as it lets the browser jump in to rescue you with a popup before you go Back.

I dont' think thats correct. This occurs in Firefox as well.

I've checked in Firefox 9 and Chrome 16.

Chrome is terrible compared to safari - the notification to the user is a very small barely visible arrow that gains visibility as the user scrolls further sideways.

Firefox is terrible compared to chrome, it just happens.

So as I said - Safari does something great, others copy it poorly, and "Lion breaks the web".

Then Firefox also copied poorly (wouldn’t surprise me).

It’s a bug in Firefox and Chrome, nothing else.

Reply on news.ycombinator.com