Safari is the new Internet Explorer. That was my experience trying to grapple with its weird, non-standards-compliant implementation of HTML5 required fields.
Safari 9.1
21–30 of 57 posts
Re: Safari 9.1
#22Re: Safari 9.1
#23> Displaying a JavaScript dialog—alert, confirm, or prompt—no longer activates the calling tab.
This seems like a regression to me. If some page is bugging me then I'd like to know which one it is so I can close it.
Re: Safari 9.1
#24I was forced to stop using Safari on my iPhone 5 because it became unusably slow after loading only a handful of simultaneous tabs. The changes came after one of the Apple updates and after that I had to switch to Chrome for iPhone.
But due to the nature of closed iOS, Chrome on iOS uses the same engine as Safari...
Indeed. Up until recently, Chrome for iOS was actually a lot slower than Safari as it was yet to switch to WKWebView from UIWebView.
Doing so yielded much better performance:
https://blog.chromium.org/2016/01/a-faster-more-stable-chrom...
Re: Safari 9.1
#25Safari is the new Internet Explorer. That was my experience trying to grapple with its weird, non-standards-compliant implementation of HTML5 required fields.
With the caveat that it's basically only on iOS and OS X.
Re: Safari 9.1
#26Earlier quoted context omitted.
Great. But as an end user I "utterly" hate the Chrome/Firefox model of endless updates.
You hate endless security updates? Endless compatibility updates? Endless feature improvements? I'm not sure what part of the dark ages you would like to return to. Are we talking pre-Chrome, pre-Firefox or the days when Netscape 4 roamed majestically across the Triassic plains?
> Endless feature improvements?
I'd be ok without these, thanks. So many improvements turn out to be regressions in usability, causing and endless cycle of "now how do I do X today?"
The compatibility updates, well, I don't recall actually seeing a lot of those day to day. So, not a lot of benefit there either.
Re: Safari 9.1
#27> Displaying a JavaScript dialog—alert, confirm, or prompt—no longer activates the calling tab. This seems like a regression to me. If some page is bugging me then I'd like to know which one it is so I can close it.
Modals alerts acting 'app-wide' rather than 'tab-wide' is a truly horrible thing. If there was a subtle indication of a tab showing a modal then it would be acceptable but this is better than the current state-of-affairs.
Re: Safari 9.1
#28For anyone wondering why anybody uses Safari these days, the simple answer (for me, at least) is that it consumes much less CPU and energy on my MacBook Pro than Chrome and Firefox. It can mean an hour or more of battery life when unplugged, and greatly reduced testicle-cooking when plugged. I still use Chrome for development but Safari is my "daily driver" for email, surfing, reading, etc.
Re: Safari 9.1
#29Great, the Safari 9.1 GestureEvent for desktop PCs is completely different on how Chrome https://bugs.chromium.org/p/chromium/issues/detail?id=289887 http://jsbin.com/cuxopid/1/edit?html,css,js,output and IE are handling pinch to zoom gestures with trackpads on desktops. Gestures on desktop like pinch to zoom is now a total mess. Where is W3C or WHATWG on this? Pinch to zoom is now on Firefox: None (there was an attempt in the past) Chrome: it's mousewheel+ctrl IE: it's mousewheel+ctrl Safari: shiny new GestureEvent
Re: Safari 9.1
#30For anyone wondering why anybody uses Safari these days, the simple answer (for me, at least) is that it consumes much less CPU and energy on my MacBook Pro than Chrome and Firefox. It can mean an hour or more of battery life when unplugged, and greatly reduced testicle-cooking when plugged. I still use Chrome for development but Safari is my "daily driver" for email, surfing, reading, etc.
an even simpler answer would be because it is the default browser..