Re: Kickoff application manifest work
Ping… anyone wanna work with me on this? On Tuesday, 14 May 2013 at 11:47, Marcos Caceres wrote: While we transition the application manifest spec from SysApps to WebApps, I'd like to kick off discussion by encouraging people to either discuss the current proposal here or over on GitHub. The current proposal can be found here: http://manifest.sysapps.org/ Repo is here: https://github.com/sysapps/manifest Things that we need to discuss: * what's the problem we are trying to solve? (scope for the work). * what actual manifest properties are useful? are any missing? * do any members need to be refactored to better meet the use cases? * how do we associate a manifest with a web page? * More open issues: https://github.com/sysapps/manifest/issues Following in the footsteps of Navigation Controller and DOM Futures, it would be ideal to have a core group of individuals helping out with this effort. If you want to be part of a core team, please let me know and I can add you on GitHub (or just add your self to watch the repository on https://github.com/sysapps/manifest) and file bugs/ask questions as you see fit. If you want to discuss the proposal directly with me, I'm marcosc IRC on both freenode (#whatwg) and w3c (#webapps). Kind regards, Marcos -- Marcos Caceres
[Bug 21137] Define key names for game controller of Android
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137 Gary Kacmarcik gary...@google.com changed: What|Removed |Added CC||gary...@google.com, ||public-webapps@w3.org Component|DOM3 Events |UI Events Assignee|tra...@microsoft.com|gary...@google.com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 21083] Proposal key names for Android
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083 Gary Kacmarcik gary...@google.com changed: What|Removed |Added CC||public-webapps@w3.org Component|DOM3 Events |UI Events Assignee|tra...@microsoft.com|gary...@google.com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 21121] Define mobile phone related keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21121 Gary Kacmarcik gary...@google.com changed: What|Removed |Added CC||gary...@google.com, ||public-webapps@w3.org Component|DOM3 Events |UI Events Assignee|tra...@microsoft.com|gary...@google.com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 21120] Define TV or A/V remote controller's keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120 Gary Kacmarcik gary...@google.com changed: What|Removed |Added CC||gary...@google.com, ||public-webapps@w3.org Component|DOM3 Events |UI Events Assignee|tra...@microsoft.com|gary...@google.com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 21136] Define Home key and Back key of Android smartphone
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21136 Travis Leithead [MSFT] tra...@microsoft.com changed: What|Removed |Added CC||public-webapps@w3.org Component|DOM3 Events |UI Events Assignee|tra...@microsoft.com|gary...@google.com --- Comment #1 from Travis Leithead [MSFT] tra...@microsoft.com --- Moving to UI Events until we define an extension doc for specific device keys like Android Smartphone. -- You are receiving this mail because: You are on the CC list for the bug.
Re: Kickoff application manifest work
On Tue, May 14, 2013 at 7:47 PM, Marcos Caceres mcace...@mozilla.com wrote: The current proposal can be found here: http://manifest.sysapps.org/ I wonder to what extent we actually need a manifest. I think it's main benefit might be in grouping a set of pages, but whether that needs to be via a manifest I'm less sure about. A requirement that keeps coming back for web applications (i.e. those served in a browser over HTTP, such as https://www.twitter.com/ ) is that multiple of them per origin should be supported. Reasoning for this is simplicity of deploying new applications and to some extent to reduce the number of DNS queries for a suite of applications. Downside of that approach is increased attack surface for a suite applications and no trivial boundary between them (given a URL it's not clear to which application it belongs). Navigation Controller solves the grouping of a set of pages using an origin plus wildcard matching for a set of URLs, although as currently proposed a subset of those URLs might be something else altogether again, without much declarative control. For event pages/workers you'll want something similar. To identify what a URL's associated event page/worker is. It might be though that maybe we should put the boundary for applications on the web on the origin level. It would certainly be extremely convenient and allow for a whole bunch of simplifications. -- http://annevankesteren.nl/
