Would love better clipboard support so we could paste images into Gmail and GitHub issues. Having to use Safari more often on a new MBP to save battery, this is one feature I miss daily.
Safari 10.1
41–50 of 169 posts
Re: Safari 10.1
#42Whew. Custom Elements, Fetch, and async/await all at once? Christmas came real early in 2017...
Too bad we still have to use shims until iOS Safari catches up (hopefully this year).
Re: Safari 10.1
#43Safari is a great browser for MacOS, what it lacks right now, is not more features, is opening the extension system. Let's face it, it is ridiculous to have to pay 100$ a year to be able to improve Apple's product in exchange for nothing. Making plugins for a browser doesn't have in any way the same opportunities to make money from it as making apps for iOS or for MacOS. Still Apple, in all their usual stubbornness r…
I don't know whether it's ridiculous or not, but it's definitely a culture clash.
Safari had a hard time attracting ports of other browsers' extensions even when you could distribute them for free and they were fully HTML-based. (Probably because there was no Windows version.) Now, not only do you have to pay, the old extension system has been deprecated in favor of a new system where you have to bundle your extension within a native app and implement a native-code-based interface. It's probably not a bad interface in isolation (haven't tried it myself), and makes it easier for existing native app developers to add extensions, but I expect it makes code reuse between extensions for Safari and other browsers quite difficult.
In comparison, both Firefox and Edge are going in the exact opposite direction and moving to an extension API directly based on, and largely compatible with, Chrome extensions. So pretty soon you'll be able to use popular extensions with any browser you prefer... except Safari.
But hey, at least now Safari will be able to take advantage of the popularity of building apps for the Mac App Store. Oh wait...
Re: Safari 10.1
#44Re: Safari 10.1
#45aside from the information: This website is sooo rediculously hard to browse on my smartphone (Nexus). The arrows are the only thing working to expand the information and they are really hard to open and close (with strange go backwards behaviour). Really bad website UX Apple.
On iOS it is a single scrollable page with a collapsed table of contents. Bad browser detection?
Re: Safari 10.1
#46I wish they made it usable, favoring function over [their idea of ]beauty.
I still can't use it because of the super-annoing "feature" that greys out tab favicons making impossible to immediately see what site is loaded in that tab if you have a lot of tabs open, and of course not showing the full address on iOS (I'm bother by the fact they think it's a good idea, but at least on macOS there's a setting to remove it).
Apple is really falling behind both Microsoft and expecially Google in terms of their own software. It's just not usable anymore. Everything is hidden just to make it look pretty. So annoying.
They should focus on their iOS version, because on the desktop the contribution they make is minimal, on iOS no one will install a custom browser instead of keeping the ad-free default one.
Re: Safari 10.1
#47Biggest deal here (for me) is the HTML 5 download attribute. Without that you cannot name or provide an extension for files that are triggered for download.
The server can do this with the Content-Disposition header. The `download` attribute just lets you trigger downloads (optionally with a filename) for URLs that otherwise wouldn't be downloaded.
It's important to download JS-generated data as well, such as something in a Blob. You can't set a HTTP header on local content. The 'download' attribute lets the user "download" that without having to wastefully post it to a server and back.
Re: Safari 10.1
#48We just need support for required as in now (; http://stackoverflow.com/q/23261301/938236 > If an attribute is not listed here, it is not supported by Safari and WebKit: https://developer.apple.com/library/content/documentation/Ap...
That seems to be a documentation oversight. The blog post announcing form validation support mentions `required` explicitly as a supported attribute: https://webkit.org/blog/7099/html-interactive-form-validatio...
Re: Safari 10.1
#49Re: Safari 10.1
#50Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new feature of OS X in ages, and is fast fast fast.