[Webkit-unassigned] [Bug 252664] REGRESSION: Previewing projects broken in Construct 3 web app with Safari TP 163

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=252664

--- Comment #21 from Ashley Gullen <ashley at scirra.com> ---
My frustration is with Apple and their management of Safari releases, not the WebKit project - my comment was in response to "Apple release dates". I accept that there is not a problem with Safari in this case. However bugs happen, and merely knowing a release date is very helpful in order to plan our response to it. All Apple need to do to avoid causing us disruption is tell us the earliest likely release date. Sure, release dates can slip, but it still provides something for us to plan around.

Apple's needless secrecy around release dates - and in other cases, even just knowing which version of Safari bug fixes are planned to ship in - has repeatedly caused us disruption and wasted time over the years, solely because Apple refuse to tell us basic information that they surely have internally. I can point to many past cases, not least of which was completely breaking WebAssembly for months and not providing any useful information about it whatsoever at any time. The secrecy is harmful to web developers and I doubt it achieves anything for Apple. Other browser vendors all have transparent processes and never cause us these kinds of problems.

This is such a frustrating and on-going problem for us, that if Apple refuse to publish basic information to help avoid causing us serious disruption, I feel like my only option is to talk to regulators and try to get them to force Apple to change. What else can I do to prevent this? For example if we get the real Chromium on iOS, at least we can give customers a workaround - but I'd much prefer it if we could make sure things keep working in Safari!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230303/3a4656dd/attachment.htm>