Safari 10.1

#1

Post by stablemap » Tue, Jan 24, 2017, 7:11 PM UTC

Safari 10.1
developer.apple.com

Re: Safari 10.1

#2

Post by therealmarv » Tue, Jan 24, 2017, 7:20 PM UTC

aside 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.

Re: Safari 10.1

#3

Post by pomber » Tue, Jan 24, 2017, 7:26 PM UTC

One polyfill less for custom elements

Re: Safari 10.1

#4

Post by ryandvm » Tue, Jan 24, 2017, 9:28 PM UTC

therealmarv wrote: post #2

aside 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.

Sorry infidel, you're not supposed to be reading this website on unblessed devices.

Re: Safari 10.1

#5

Post by jbmorgado » Tue, Jan 24, 2017, 9:33 PM UTC

Safari 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 refuse to let people to publish and sign their extensions for Safari without paying them their 100$ anual fee.

Re: Safari 10.1

#6

Post by dcgudeman » Tue, Jan 24, 2017, 9:33 PM UTC

Support for fetch and async/await, that's pretty big news.

Re: Safari 10.1

#7

Post by tdumitrescu » Tue, Jan 24, 2017, 9:34 PM UTC

Whew. Custom Elements, Fetch, and async/await all at once? Christmas came real early in 2017...

Re: Safari 10.1

#8

Post by thatmiddleway » Tue, Jan 24, 2017, 9:35 PM UTC

Lack of custom elements has been a big problem for years. Glad they finally caught up there. We can finally use semantic HTML with safari!

Re: Safari 10.1

#9

Post by coldtea » Tue, Jan 24, 2017, 9:38 PM UTC

therealmarv wrote: post #2

aside 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.

It's not meant for mobile use any more than a Javadoc webpage is.

It's a developer resource to consult while coding on your laptop.

Re: Safari 10.1

#10

Post by jbmorgado » Tue, Jan 24, 2017, 9:39 PM UTC

I don't understand the down votes since it's factual that you can't sign your plugins and distribute them inside Safari (AND ALSO keep them automatically updated) unless you pay Apple their anual fee.

But well, fanboys will be fanboys.