WebView definition not covering all types of WebViews

Vertical Standard Comment

Standard Version (see README.md for info): V0.0.9

Line Number: 377

Clause/Subclause:

Paragraph/Figure/Table: 3.1

Comment

The current definition leaves out other WebViews like Custom Tabs and SFSafariViewController. Additionally I wouldn't call frameworks/tools Electron or Tauri WebViews. They use WebViews to provide applications.

See: https://webview-cg.github.io/usage-and-challenges/#webviews

WebView Types

Browser-like WebViews should have the same user agent duties, requirements, security measures as browsers. They are used for web browsing use cases after all and users expect from this InAppBrowser/embedded experience the same things as from standalone browsers.

Fully-fledged WebViews are immensely powerful and used in very different ways. The implementations that are out there to do also differ quite a bit. Therefore it's a lot harder to write down all requirements and risk assessments.

Proposed Changes:

Not sure how to better phrase it but the two types of WebViews are important to distinguish.

A embedded browser component, often provided by an OS platform that enables applications to display web content within their user interface, providing a subset of full browser functionality while operating under the security context and lifecycle of the host application. Common implementations include Android WebView, iOS WKWebView, Windows WebView2, GeckoView. Some WebView APIs like Android Custom Tabs and SFSafariViewController are built for browsing the web and follow the browsers security models.