Hacker News Reader

Comment by kylec | Hacker News Reader

Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.

View on HN

Safari is the new IE.

They really are doing themselves a long term disservice by letting this meme be absolutely true.

Hoping for the day I can use Service Workers in all mobile browsers.

Scrolls fine in Firefox, Edge, and IE11, so yeah. It's Safari.

Scrolling works fine in Safari unless you override the native functionality with a buggy/insufficiently tested script.

We will be fixing this. There was a change in safari that busted our material design lite usage.

FYI: It still doesn't work in Safari(9.1.1)

It breaks in almost spectacular way: https://vid.me/hPye

I really wonder what really causes it.

While we're mentioning bugs, there is a pretty large header misspelling on the site with "Progressive Web Aps" (should be Apps)...

I'm glad these folks spend their time on Chrome dev tools rather than catering to the users of inferior browsers who expect people to invest extra energy catering to their preferences.

Edit: This may help: https://www.mozilla.org/en-US/firefox/new/

Whilst the issue may not be the fault of the web designers, there's not really any need to call Safari inferior. It's probably a bug, all browsers have them.

My main issue, FWIW, is not that Apple don't fix bugs - it's the long timeframes they take between releases!

Rarely is any description 'needed', but in this case it is 'helpful'. The parent seems to be unaware that Safari has, over time, become inferior (relative to the other popular browsers) increasing the likelihood that the problem is with safari rather than with the site. Being unaware of the inferiority of safari, he didn't even try another browser. Simply knowing that its a safari bug may not be sufficient to maximize the efficiency of his problem solving strategy in the future, as he may brush this off as anomalous. Knowledge that others have found safari increasingly buggy and inferior makes it more likely the parent may adopt a better strategy, such as 'test with another browser first'

What, specifically, do you consider inferior about Safari? I'm genuinely curious - I use Chrome, Firefox and Safari regularly and I find Chrome and Safari to be of equal quality. And I notice bugs in Chrome every now and then, but with both browsers I find it pretty rare these days.

Well, as a for-example, safari's support for indexeddb, service workers, push notifications, and just about everything that makes progressive web apps interesting is pretty lacking.

As another for-example, I was able to hard-crash safari on ios by setting some CSS attributes on the scroll track about eight months ago - like literally a web page with css that altered how wide the scroll bar track was could CTD safari on ios.

As another for-example, KeyboardEvent.key isn't supported in safari.

As another for-example, http://caniuse.com/#compare=chrome+51,safari+9.1,ios_saf+9.3 and scroll down. Battery Status API, Fetch API, Proxy Objects, Shared Web Workers, on and on. The "modern" web as a good platform for interesting progressive apps is passing safari, in particular iOS users, by.

One assumes a motivator here is the app store: apple's walled garden approach is fundamentally incompatible with web apps gaining all these APIs, whereas android's (relative) openness means Google is less uptight about people deploying apps without going through the app store approval process.

My view is that Safari is leading in privacy and lags in everything else. Meanwhile Chrome absolutely leads in security while Firefox leads in standard support.

I use Chrome for work and Safari for casual browsing. Safari definitely has better tab management (tab expose). I am also sad that Firefox UI looks stale. Their settings & options window look like it hasn't changed since initial release.

The settings window changed - it is now a full screen tab.

In any event, Safari is perfectly capable of scrolling a page.

You certainly have made a lot of assumptions about me. I did test in other browsers - Chrome, obviously, and Firefox. But the fact that it works in Chrome and Firefox doesn't excuse the fact that it doesn't work in Safari. I'm a web developer, so it's my job to make things work correctly in all the browsers, Safari included, so from my perspective the creator of the page did a bad job.

Worse, it wasn't something fancy that it's understandable isn't supported in older browsers - it was scrolling, something that literally every web browser ever has been able to do.

Finally, as a web developer and as someone that has used Safari as his primary browser for many years, I rarely have an issue with Safari being "buggy and inferior". You may not get cool new APIs first, but Safari is usually pretty solid and bug-free with the ones it does support.

We will be fixing it. It was a bug in Material Design Lite and we need to upgrade.

You have a shitty attitude.

How can you seriously think that Google developers not supporting other browsers than Chrome is ever a good thing? We are already headed quickly enough towards a Chrome monopoly and Google abusing their dominant position on the internet to make other browsers look bad isn't making that any better.

> expect people to invest extra energy

Funny you use that phrase, because that's what Google expects me to invest to use their bloated excuse of a browser.

I mainly use Safari since it has such a performant UI that doesn't chew up battery-intensive CPU cycles all the time.

Reply on news.ycombinator.com