The EU should leave well enough alone. If Apple wants to have a closed box model, let them. Those of us who want a more open system have Android. And if I did use an iPhone with these provisions in place, I'd still use iStore. Sideloading apps or using third party stores (which I would interpret to mean stores not controlled by a manufacturer) has been the source of a lot of grief in the Android world.Looks like the EU might try and force apple to allow other browser engines
A leaked version of the European Union's Digital Markets Act (DMA) indicates that Apple could be forced to make major changes to the App Store,...www.macrumors.com
The issue with HEIC is that no browsers support it. None of them. Not even Safari (seriously).
It works as a format for viewing on iOS and macOS and sharing with other devices that may support it but there are currently no web browsers in use today that natively support displaying that format on the web.
That all being said, my experience is not the same as yours.
Whether I upload pictures from my Photos library to Safari on iOS or macOS the pictures already upload as a jpeg file, and providing the server has EXIF extensions enabled in PHP, it should automatically orient them correctly.
If your experience is different, what exactly are the steps you are taking to reproduce the issue? And do you experience the same issue trying to upload photos to this forum?
xenforo is ahead of technologyCurrently the main issue appears to be that while permission is granted to allow notifications for a given site, Safari doesn't actually accurately report that back.
That's a Safari issue, more than an XF issue. You can see the same on various Web Push API samples; permission is granted but it never appears to be.
(Side note: There is a Permissions API experimental feature too but enabling that has no effect).
To clarify comments surrounding a future version, it is feasible, though not entirely certain, that the web push library we use might need changes in order to work with Safari and maybe iOS in future. If that is the case, XF 2.2 may be constrained and not be able to upgrade to the version that includes those changes.
XF 2.3 is already using a higher version because we're able to due to increased PHP requirements (7.2.5 and above).
Early days but this certainly is encouraging. Interestingly the addition is not mentioned in any of the previous 10 or so WebKit change logs that I checked. This could also mean that the powers that be either didn't intend to include it, or they know it's incomplete.
The timing of all of this, however, could well mean that we're looking here at features which may become stable in macOS 13 and iOS 16. Though it would be nice if it ended up being in a second-point release rather than a headline feature of a major release.
Or maybe not…
One can only dream.
That seems like a question you should send a ticket in for, but based on publicly available information, I'll give you an answer. There is no ETA that the general public is aware of, and you aren't going to get an answer.
XF 2.3 is targeted for release in 2022.