![]() Not a bad response in the end, and good work by Apple employees. After some confusion about whether the issue was a duplicate of another (it wasn't), Apple engineers investigated, identified the problem, and said they had it fixed by February 27th. I duly reported the issue on February 17th. Potentially this also means many uses of zip.js across the web are broken too. Safari 16.4 added support for the Compression Streams API, but it was somehow incompatible with zip.js, which meant opening projects in Construct usually failed. Breaking opening projectsĬonstruct projects are based on zip files, and we use a popular library zip.js to read them, which in turn uses the Compression Streams API when supported. So when Safari 16.4 beta 1 was announced on February 16th (also not to any public schedule), we started taking a closer look - and there were a lot of problems. ![]() However when things start making their way to beta, it's time to look more closely. Pre-release browsers are usually pretty rocky with obvious issues that get sorted out soon enough. Apple provide Safari Technology Preview (STP), but it's only for macOS, and does not update to any public schedule. For example Chrome Canary and Firefox Nightly update daily, and there's also less frequent dev and beta releases. Most browsers provide pre-release versions for early testing. I wanted to share our experience so customers, developers, regulators, and Apple themselves can see what we go through with what is supposed to be a routine Safari release. Early versions of Safari 16.4 broke opening projects, previewing projects, and all existing content published with Construct, all in different ways. We make the browser-based game creation app Construct. Safari 16.4 rolled out last week, and for us it's been a nightmare.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |