Standardization Tasks - PeterWangIntel/crosswalk-website GitHub Wiki
We have identified a set of standardization tasks that we need to get started with. We hope to get to a point where we have clear visibility and accountability for contributions from each team/site, assuming responsibility for sub-tasks of Crosswalk.
The page shares its basic structure and boilerplate with Development tasks for consistency.
On a high-level, we would like to see the Runtime and Security Model for Web Applications (partially obsoleted as of 2013-09) spec to better consider and address non-mobile use cases e.g. desktop web browsers, and web runtimes in desktop context. We believe the current spec is too focused on mobile use cases. For example, parts of the spec (e.g. Application Lifecycle and Events) address issues relevant to web browsers and regular web apps too. We should split these parts out i.e. modularize the currently monolithic specification.
Relevant W3C working groups:
- SysApps working group (public-sysapps) - Runtime and Security Model, Package Format (incl. Web Manifest extensions for Packaged Apps), SysApps APIs
- WebApps working group (public-webapps) - Web Manifest
Status: draft spec available
Application Lifecycle and Events draft is being worked on in the SysApps working group. See the draft for use cases, requirements and the draft spec.
Status: exploring
The Web Manifest spec is scope for the WebApps working group, targeted at regular web apps. Extensions specific to Packaged Apps to be specified in the SysApps working group.
The "event page" and Web Manifest integration to be specified. Pointers to relevant discussion on public-webapps for follow-up: event pages/workers synchronous access to its visible tabs, the grouping of a set of pages using an origin plus wildcard matching
Status: exploring