“Manifest API” has always been a thing. It’s only for extensions and DO NOT affect website support. You’re misreading the situation with Manifest v3 almost completely. Here, “Manifest” refers to the API used for extensions. The biggest differences are 1. Switching from always-on pages to services 2. Sabotaging the Adblock API, basically. User agents are unaffected. Websites do not care about it (except those who are anti Adblock).
You may be confusing things with WebEnvironmentIntegrity, which has been canceled with the team shifting focus to an Android-exclusive WebViews API which I haven’t studied yet.
“Manifest API” has always been a thing. It’s only for extensions and DO NOT affect website support. You’re misreading the situation with Manifest v3 almost completely. Here, “Manifest” refers to the API used for extensions. The biggest differences are 1. Switching from always-on pages to services 2. Sabotaging the Adblock API, basically. User agents are unaffected. Websites do not care about it (except those who are anti Adblock).
You may be confusing things with WebEnvironmentIntegrity, which has been canceled with the team shifting focus to an Android-exclusive WebViews API which I haven’t studied yet.