Apple to Patch Web Browser Vulnerabilities Affecting Recent Macs, iPads and iPhones

[burgman]

They’re working on a new version of it called AppleSeek. At the moment, they’re “seeking” Chinese engineers who know what they’re doing.

Problem is finding some who can pass background checks in the new reality of 2025

 

[MacHeritage]

Yup, I'm slowly moving away from Safari and using Firefox more. There are a little issues here and there in Safari that Firefox never seems to have.

I know and yet it is all based on the same WebKit of iOS. That is what is puzzling to me. They must take the extra time to be perfect with WebKit since they don't have to make their own engine run on iOS (a lot more work).

Firefox on Android with its own engine is terrible compared to Safari.

 

[DeepIn2U]

I know and yet it is all based on the same WebKit of iOS. That is what is puzzling to me. They must take the extra time to be perfect with WebKit since they don't have to make their own engine run on iOS (a lot more work).

Firefox on Android with its own engine is terrible compared to Safari.

You haven't really been using Firefox on Android at all lately.
I use it everyday on my S23 for 6 months now. Yes there is that gawd annoying and finnicky UI issue where I have to minimize the UI drawer to get to the bookmarks but that is the only issue I've faced rendering ANY website or pdf document.

 

[MacHeritage]

You haven't really been using Firefox on Android at all lately.
I use it everyday on my S23 for 6 months now. Yes there is that gawd annoying and finnicky UI issue where I have to minimize the UI drawer to get to the bookmarks but that is the only issue I've faced rendering ANY website or pdf document.

I am for testing purposes using a whole range of phones using the latest versions and older for each. Firefox on Android was way worse at rendering certain troublesome combinations of HTML/CSS code I was dealing with but on iOS using WebKit (like all other iOS browsers) was better than Safari on iOS. That is what I was saying in the posts above. That is why I wouldn't want Firefox's engine on iOS. It is easy to make a web site work on iOS, no matter the browser. But Firefox was even better than Safari, which I was surprised by, since they are both using the same WebKit engine.

The only reason you don't encounter the issues with most browsers is because of us webmasters making sure those web sites ship with all of that in mind and re-code for "Any Browser Having An Issue" to make it work on your end across the board. That is the reason some browsers have issues with one site and not another: the webmaster/coder/person didn't bother to test the browser properly or too lazy/burned out to bother fixing it, if they did test it.