WebView CG Update

Key Takeaways

• WebView CG Overview
• What we've been working on

WebView CG

The Community Group aims to identify, understand and reduce the issues arising from the use of software components (typically referred as WebViews) that are used to render Web technology-based content outside of a Web browser (Native Apps, MiniApps, etc).

Charter

WebView CG Scope

• identify representative use cases of where WebViews are being used, regardless of the platform and type of device they're used on,
• identify the issues that arise from these usages,
• determine whether these issues can be addressed through improvements to the Web Platform, the surrounding ecosystem (e.g. documentation, testing frameworks) or through other mechanisms,
• raise awareness about the impact of WebViews for Web technologies in relevant communities (e.g. existing W3C groups)

Use cases in discussion (1/2)

• Load a WebView page
• Origin in a WebView for locally hosted content
• Requests/responses sharing and proxy between Native and WebView
• Render WebView Components and Native Components in same layer
• Inject custom JS scripts
• Control API permissions

Use cases in discussion (2/2)

• Display and manipulate third party content while blocking third party scripting
• Define different types of WebViews
• Manage web storage and cookies
• Disable web platform features and web APIs
• Intercept / modify network traffic
• Gather Diagnostic Data

WebView CG Report

Thanks for your time!

• Feel free to reach us Qing An, Rayan Kanso
• Find us at https://www.w3.org/community/webview