Re:W3C Proposes the Creation of a WebView Community Group
by melony on Wednesday May 11, 2022 @09:44AM
(#31339837)
OP was referring to the use case where webviews extend your native mobile app functionality.
Re:W3C Proposes the Creation of a WebView Community Group
by lucideer on Wednesday May 11, 2022 @10:41AM
(#31340636)
OP was using that use case as their example, but this is about standardisation so it needs to fit a range of use cases, most importantly the common ones.
How do you restrict one use case and not another? If a restriction is opt-in in a standard it's not useful.
> With webviews however, that model doesn't make much sense: the embedder is controlling the webview and frequently needs to apply or enrich the embedded view.
This isn't necessarily the case - it's certainly often been the assumption, but I don't think maintaining status quo here is a self-evident good.
Common case: I click a link in an email client / social media feed and it opens in a webview controlled by that app. It's a 3rd-party link either sent to me by an email contact, or posted by some private individual using the social media platform: it's not necessarily owned/controlled by the developer of the app, and as a user, I have no strong desire for the app to have direct access to that content.
The iframe comparison fits quite well in my mind, and most of the concerns / ideals hold true.