-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge use case of issue 7 #25
Conversation
Merge use case of #7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a bunch of comments about non-mobile app use cases
index.html
Outdated
|
||
<dt>Motivation</dt> | ||
<dd> | ||
<a href="https://appfigures.com/top-sdks/development/all">Up to 30%</a> of apps found in the App stores (Apple and Google) are built with frameworks like <a href="https://cordova.apache.org">Apache Cordova</a> and <a href="https://capacitorjs.com/">CapacitorJS</a>. Those two frameworks use one big Webview for providing app developers a native wrapper and some plugins for their Web App. App developers build their Web application and put the HTML, CSS and JavaScript files in one folder. The framework then takes care of building a Native App project and bundling the Web code as a Native application ready to distribute via the App stores. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem also exists on desktop platforms and their web views as well, both for applications (in Electron, etc.) or books.
index.html
Outdated
<dt>Stakeholders</dt> | ||
<dd> | ||
<ul> | ||
<li>WebView provider: Apple, Google, deciders on how to support having a standardized origin of web content hosted by the App for the Webview</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also need to include desktop providers including Microsoft and various Linux variants.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also the Publishing CG & WG here at the W3C, as they manage the EPUB standard
index.html
Outdated
|
||
<dt>Analysis</dt> | ||
<dd> | ||
Apps built with this hybrid approach in mind are really dependent on making CORS work and HTTP requests possible on their own web content. This approach might benefit from a standardized way of providing web content from the app to the webview. This content could be considered secure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of the extra considerations for non-applications (i.e., eBooks) is that the content is user generated (UGC) and therefore not reviewed as part of an AppStore review. It is also not digitally signed - so there is really no "trust" associated with it and therefore security becomes a significant concern
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with it. I only tried to fix some typos and add some words to make it a bit more clear. Please check again.
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
Co-authored-by: Niklas Merz <[email protected]>
I go ahead and merge the current PR. https://webview-cg.github.io/usage-and-challenges/#the-origin-in-a-webview-for-locally-hosted-content If any new edits, please make PR freely. |
Merge use case of #7