Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New WebKit Features in Safari 13.1

webkit.org

Post reply on HN
Print view View original

31–40 of 60 posts

Re: New WebKit Features in Safari 13.1

#31

Post by andrekandre »

> Async Clipboard API

> The implementation is available through the navigator.clipboard API which must be called within user gesture event handlers like pointerdown or pointerup, and only works for content served in a secure context (e.g. https://). Instead of a permissions-based model for reading from the clipboard, a native UI is displayed when the page calls into the clipboard API; the clipboard can only be accessed if the user then explicitly interacts with the platform UI.

that looks pretty cool... do other browsers implementation also work like ↑ that?

Re: New WebKit Features in Safari 13.1

#32

Post by scarface74 »

maxwell wrote: post #10
forkLding wrote: post #4

At least I think WebRTC was mentioned, been dying for more fixes to issues.

Apple has intentionally crippled WebRTC for years to stifle FaceTime competition and drive up dev costs by forcing native app development. The video chat startup I co-founded in 2015 was impacted. https://docs.house.gov/meetings/JU/JU05/20190716/109793/HHRG...

Why pray tell would Apple want to “stifle” competition for FaceTime? It’s not like Apple makes money from it.

And then they are stifling competition for their app - by “forcing” you to create an app that integrates with dialer and your call history?

Maybe your startup was “impacted” by not having the expertise or funding to create a native app like at least a dozen companies have done?

Re: New WebKit Features in Safari 13.1

#33

Post by 1over137 »

scarface74 wrote: post #32
maxwell wrote: post #10

Earlier quoted context omitted.

Apple has intentionally crippled WebRTC for years to stifle FaceTime competition and drive up dev costs by forcing native app development. The video chat startup I co-founded in 2015 was impacted. https://docs.house.gov/meetings/JU/JU05/20190716/109793/HHRG...

Why pray tell would Apple want to “stifle” competition for FaceTime? It’s not like Apple makes money from it. And then they are stifling competition for their app - by “forcing” you to create an app that integrates with dialer and your call history? Maybe your startup was “impacted” by not having the expertise or funding to create a native app like at least a dozen companies have done?

>It’s not like Apple makes money from it.

Facetime is a feature that helps sell their devices. If they don't ultimately make money from it, why did they spent money to create it?

Re: New WebKit Features in Safari 13.1

#35

Post by scarface74 »

1over137 wrote: post #33
scarface74 wrote: post #32

Earlier quoted context omitted.

Why pray tell would Apple want to “stifle” competition for FaceTime? It’s not like Apple makes money from it. And then they are stifling competition for their app - by “forcing” you to create an app that integrates with dialer and your call history? Maybe your startup was “impacted” by not having the expertise or funding to create a native app like at least a dozen companies have done?

>It’s not like Apple makes money from it. Facetime is a feature that helps sell their devices. If they don't ultimately make money from it, why did they spent money to create it?

So how would stopping people from making web video chat apps but allowing them to make apps that integrate with the dialer and phone history help them sell more devices?

They want a robust third party ecosystem.

Re: New WebKit Features in Safari 13.1

#36

Post by lilyball »

tmvnty wrote: post #20

I do love browse with Safari from time to time, but it would not take long for me to notice a site's behaviour being "different" because of it. Use hn.algolia.com as an example, on Safari 13.1, the site currently renders differently to Chrome (black background?) and the time range filter (Past Year/Month etc) text are missing...

The dropdown buttons appear to have customized the background color but not the text color. This leaves the text color at `color: buttontext`, and this color value changes with macOS Dark Mode.

This is probably also why clicking on any of the buttons causes the text to vanish during the click. It's turning white, because the default for an active button is `color: activebuttontext`.

Re: New WebKit Features in Safari 13.1

#38

Post by claytongulick »

Still doing everything they can to hold back PWA's, I see.

Their browser monopoly on ios can only last so long. The same strategy backfired horribly for ms in the ie6 days.

(And no, you can't install an alternate browser on ios. It's just a crippled "skinned" shell on top of safari)

Re: New WebKit Features in Safari 13.1

#39

Post by Tagbert »

gumby wrote: post #28
tmvnty wrote: post #20

I do love browse with Safari from time to time, but it would not take long for me to notice a site's behaviour being "different" because of it. Use hn.algolia.com as an example, on Safari 13.1, the site currently renders differently to Chrome (black background?) and the time range filter (Past Year/Month etc) text are missing...

Is this a bug in WebKit or in the algolia site?

It’s usually considered best, when styling a site, that if you set the background color, you have to set the text color. otherwise you run into site bugs like this. Dark Mode is one cause but there are other reason why text might not be the color you expect and your background color will conflict.

Re: New WebKit Features in Safari 13.1

#40

Post by Gaelan »

maxwell wrote: post #10
forkLding wrote: post #4

At least I think WebRTC was mentioned, been dying for more fixes to issues.

Apple has intentionally crippled WebRTC for years to stifle FaceTime competition and drive up dev costs by forcing native app development. The video chat startup I co-founded in 2015 was impacted. https://docs.house.gov/meetings/JU/JU05/20190716/109793/HHRG...

This is all that PDF has to say about WebRTC:

> WebRTC for videoconferencing is not supported for third-party browsers because Safari displays a prominent UI to make sure the user knows when a website is recording using the camera and microphone. Apple does not yet have a way to make this UI work in other WebKit clients.

That's a far cry from what you're insinuating.

Post reply on HN