Is it possible that 0 is adding the number 0 there instead of the string with quotes around it? (Like this tabIndex="0") <a href="https://discussions.apple.com/" tabIndex="0">Click here</a> Not sure if you are using a framework like React but the {} look like an expression to evaluate verses a string value. Double check what it is showing as in the browser's element inspector as well.

It looks like it depends on the functionality you are building using HTML5 technologies. I would imagine Cordova and React Native would be fine. This thread seems to be discussing something similar. https://developer.apple.com/forums/thread/128362 There is a news post as well that links to the guidelines. https://developer.apple.com/news/?id=01212020a

If you connect your iPhone to your Mac with a Lightning to USB-C cable, under the "Develop" nav option (which you have to enable in Safari's preferences | "Safari Settings > Advance > Show Develop Menu in menu bar"). Under Develop, find your phone and then click the site you want to override request or responses for. Then you will have access to the Safari Developer Tools for that mobile webpage. Go to "Network", find the request you want to edit. Right click and pick if you want to override the request or response. Then edit the file there. I believe you could edit the HTML, request headers, ect... this way.

Tough to give clear advice without looking at the Angular JS you are using. One thing to note is that on iOS all browsers are using Safari's underlying technology. Meaning Chrome on iOS Is basically a re-skined version of Safari. Similar to how Edge or Brave are using Chromium under the hood for desktops. https://news.ycombinator.com/item?id=25850091#:~:text=to%20Apple%20Silicon-,On%20iOS%20there%20are%20no%20web%20browsers%20other%20than%20Safari,skins%20on%20top%20of%20Webkit. It may be good to isolate your issue to only Safari and a version of Safari. Try testing on Chrome on a Macbook and Safari on the Macbook. Try to isolate the issue! Then maybe make a copy of your app and strip everything down to the one area you believe the issue is happening and then iterate fixes from there. Double check JS features you are using here as well. https://caniuse.com/

https://www.youtube.com/watch?v=ei1sNP2zAhA

It had something to do with how it was packaged.

comment on the question

fake comment

test

fake reply

Are you using this to debug webpages or for webviews in an app?

Are you using absolute or relative image urls?

comment two

Any followup on this?