undefined | Better HN

0 pointsmadeofpalk8y ago0 comments

I couldn't disagree with this any stronger.

I think you're misunderstanding how much of a difference there was between the rest of the browsers and IE.

Besides, your claim the 'wins' Safari has had - first browser to implement ES6 in its entirety a year or so back. Chrome still doesn't support features users/clients actually ask for, like CSS Scroll snap points for making carousels http://caniuse.com/#search=scroll-snap-type

0 comments

6 comments · 1 top-level

npolet8y ago· 5 in thread

Sure, a few years ago the difference between browsers was really quite large. But we're in 2017 and most of the most used browsers are mostly in line with the supported features and expected behaviour of them.

But... safari is now the one that has weird behaviour that does not occur in Firefox, chrome and edge. Just because historically there was a massive split in behaviour doesn't mean that Safari gets off free. It's the one browser I hate testing because there are usually edge case and unexpected behaviour.

madeofpalkOP8y ago

Again, I'm not seeing this.

I look at Firefox and some of it's inconsistent behaviours around flexbox compared to other browsers (mind you, some of these are due to the spec). Just today I had an irritating render bug in Chrome.

I know, this all comes down to hearsay and individual experiences. But I still strongly believe that 'Safari is the new IE' is nothing but baseless FUD.

adrr8y ago

How have you not noticed any of them? Most obvious is local storage throws out of space exceptions if Safari is in private mode. I'm not even a web developer.

2 more replies

ricardobeat8y ago

Can you provide examples of "weird behaviour"?

Im also a Safari user, and in the majority of cases the reason it is not supported is because the page/app uses some custom Chrome-only, non-standard feature. Like this one.

madeofpalkOP8y ago

Sure. This one https://s.codepen.io/joshhunt/debug/ZKyYNz. It differs to IE, Safari and Chrome in the way it treats height:0 padding-top: 100% on a flex child. In Safari, the grey box expands properly to contain all divs. In Firefox, it doesn't.

Granted, this is more of a flexbox spec issue (last time I checked this behaviour is intentionally undefined), but it's still an annoying case of one browser doing something all the others don't.

dgrove8y ago

Widevine is not a "Chrome-only" feature. Firefox, Edge and even Opera have Widevine support.

1 more reply

j / k navigate · click thread line to collapse

0 comments

6 comments · 1 top-level

npolet8y ago· 5 in thread

madeofpalkOP8y ago

Again, I'm not seeing this.

I know, this all comes down to hearsay and individual experiences. But I still strongly believe that 'Safari is the new IE' is nothing but baseless FUD.

adrr8y ago

How have you not noticed any of them? Most obvious is local storage throws out of space exceptions if Safari is in private mode. I'm not even a web developer.

2 more replies

ricardobeat8y ago

Can you provide examples of "weird behaviour"?

Im also a Safari user, and in the majority of cases the reason it is not supported is because the page/app uses some custom Chrome-only, non-standard feature. Like this one.

madeofpalkOP8y ago

Granted, this is more of a flexbox spec issue (last time I checked this behaviour is intentionally undefined), but it's still an annoying case of one browser doing something all the others don't.

dgrove8y ago

Widevine is not a "Chrome-only" feature. Firefox, Edge and even Opera have Widevine support.

1 more reply

j / k navigate · click thread line to collapse