There was a lot of discussion around Safari 15.4 beta supporting Web Push on iOS but a ton of other great highly demanded features are coming.
Just a few highlights:
* RegExp lookbehind assertions
* outline following border-radius
* Declarative Shadow DOM
* WASM SIMD
* OffscreenCanvas (2D only for now)
Check out the beta or a recent STP release. We welcome feedback, including what you’d like to see next.
https://developer.apple.com/documentation/safari-release-notes/safari-16_4-release-notes
@AshleyGullen we are evaluating this, but it’s likely we will still ship the 2D support before 3D. We believe it is conforming per spec to support OffscreenCanvas without WebGL. And it should be feature detectable (just try making a gl context in an OffscreenCanvas and see if it fails). How much is the impact to update the feature test?
@othermaciej We did add feature detection, but only for the existence of OffscreenCanvas, because we did not anticipate anyone shipping only some contexts. Since Safari supports WebGL in OffscreenCanvas in the DOM it is not actually possible to feature detect this prior to creating a worker, which makes feature detection even harder
@othermaciej I can't understand why Apple would do this - what did they expect to happen to all existing OffscreenCanvas WebGL content? Why not postpone it for a release and ship with WebGL support to be on the safe side?
Postponing makes sense here. It's not like we haven't already waited ~4 yrs for this to hit FF and Safari ;)
https://caniuse.com/offscreencanvas
(I would love 2d support but if shipping only 2d means things will break, I can wait)
@rgadellaa @AshleyGullen I'm not able to discuss scheduling questions in detail on Mastodon. If anyone is aware of breakage besides the Construct framework, let us know, so we have all the relevant information.
@AshleyGullen This was a bug in an earlier beta. The intent is that OffscreenCanvas will not support "webgl" contexts regardless of whether it's on a worker. Expect to see that fix in an upcoming beta, it should allow for easier feature detection. https://bugs.webkit.org/show_bug.cgi?id=253267
@othermaciej We already have updated it, but it affects all content published by users of our app for the past couple of years, and they will all need to re-publish their content to avoid being affected. It's a collossal job to ask everyone to do that and I would be surprised if even 10% of customers did that prior to the Safari release.