mondrianbox wrote: ↑11 September 2024, 10:39
I have HTML/CSS coding experience, and would definitely
like to hear more about the Safari side of this situation, if you would. Thanks!
Following up real quick, sorry about the slow reply. First, a silly metaphor:
BGA is a mountain. Lightning strikes a boulder, which rolls down the mountain.
BGA staff are in charge of the whole mountain, and start installing lightning rods and securing boulders to prevent this in the future.
BGA devs are maintenance workers -- I'm scouting the mountain, reporting damage, and maybe fixing small things.
When I report that problems started happening when lightning struck, I don't mean lightning is the ONLY problem. You are frustrated because a boulder ran over your car!
Now back to the technical side, I and other devs are definitely aware of iPhone / iPad reports. I talked to a dev recently who only has iOS devices, not Android. I personally worked with a player's reports recently to correct iOS behavior on a certain game. We don't mean to ignore your problems!
The challenge is, once the Chrome 128 situation hit, BGA started brainstorming ways to fix it. The challenge is to support old Chrome/Edge, new Chrome/Edge, Safari, Firefox (and maybe other browsers, but these are probably most common). The first try used "viewport" which has pros and cons -- it is more of a "quick fix" just to keep most users playing on mobile.
Some games may still use this viewport workaround, which may affect Safari too!
After the quick fix, BGA added another scaling option ("autoscale") which should (hopefully?) work the same on all browsers.
However, some games were created long ago, or use unusual techniques because many volunteers programmed them. Because of the sheer number of BGA framework / dojo framework / browser combinations, there may be many small details which are now awkward since their assumptions are no longer met. Again, this may affect Safari.
Lastly, I think I have heard, but not personally verified, that in some cases Safari may even use the Chrome render engine instead of the normal iOS render engine.
"Why don't you leave working games alone?!"
As devs, we would love to! We don't enjoy wasting our time either.

Unfortunately they WEREN'T working for everyone, so please forgive us as we work through this challenge.
"Why don't you have a simple solution which works on all browsers?!"
BGA is basically a collection of 1000+ different pieces of software. They have common elements, but not every one works the same. Making a fix that affects 1000 pieces of software the same is nearly impossible, and we have not found a perfect way to do it. Instead, some general fixes were made, and now we are working through the most popular games to find reported problems we can reproduce.
As a reminder I am just a passionate dev, not on the BGA staff, so this is just my understanding as I try to improve the platform for all of us.