Sorry Art but the W3C disclosed the story on this list without advising
us (and disclosed/archived the original email containing some private
details without any authorization), we know why, it's probably
understandable (although questionable), why on this list and why we
should not respond here
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26478
Travis Leithead [MSFT] tra...@microsoft.com changed:
What|Removed |Added
Status|NEW |RESOLVED
I've posted the notice on the editor's draft as suggested below. If there is
help to continue to advance the direction of this spec, I'd love to see it
continue to evolve.
Note, that our Chinese Bing home page (http://www.bing.com/?mkt=zh-CN) employs
the use of a version of this API (prefixed,
Importing needs to be manipulated by script. But it's too verbose to use
script always.
If link tag can be inserted in body tag, and inserts importee's
document.body to importer, then it would be easily without any scripts.
An example is below:
component.html:
!DOCTYPE html
div
p
Cool. Want to write it up as a small extension spec? We have a new Incubator
Community Group coming up soon that would be an ideal place to drop a small
spec into and let implementers experiment with it and get broader community
feedback on the idea.
From: a...@scirra.com
On 17 Jun 2015, at 18:11, Kostiainen, Anssi anssi.kostiai...@intel.com
wrote:
On 02 Jun 2015, at 00:58, timeless timel...@gmail.com wrote:
http://www.w3.org/TR/2015/WD-appmanifest-20150212/
Thanks for the detailed review. The pull request with you review feedback
baked in is at:
