There are probably hundreds of new APIs that have come after 2012 or whatever the year was when the ball was dropped. Those were just "from the top of my head" not something to be nit picked.
I didn't also literally mean that they are currently implemented by all of those browsers today. My point is that I expect them to be implemented browsers other than Safari sooner or later as they have strongly signaled. Safari has not signaled anything about them. Or if they have, provide evidence of it and I will apologize.
> filesystem is proprietary chrome tech, dropped from standard track
>I didn't also literally mean that they are currently implemented by all of those browsers today. My point is that I expect them to be implemented browsers other than Safari sooner or later as they have strongly signaled. Safari has not signaled anything about them. Or if they have, provide evidence of it and I will apologize.
Has Android's mobile Chrome browser signalled anything more?
Because for years it has been even MORE behind Mobil Safari regarding speed and capabilities.
(And let's not even get started on the crap-fest that was Android's default browser).
I didn't also literally mean that they are currently implemented by all of those browsers today. My point is that I expect them to be implemented browsers other than Safari sooner or later as they have strongly signaled. Safari has not signaled anything about them. Or if they have, provide evidence of it and I will apologize.
> filesystem is proprietary chrome tech, dropped from standard track
That's not the file system API I am even referring to. I am referring to https://w3c.github.io/filesystem-api/ which is edited by Mozilla.
> rtc is fair, and in development
For iOS Safari? WebKit having WebRTC is completely different from iOS safari having it.