Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Marcos Caceres
On Tuesday, December 3, 2013 at 3:01 PM, Jonas Sicking wrote: > On Tue, Nov 26, 2013 at 1:02 PM, Marcos Caceres (mailto:w...@marcosc.com)> wrote: > > The Editors would appreciate if people take a look and see if you agree > > with the feature set. > > What I think we should have is something

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Boris Zbarsky
On 12/18/13 5:58 AM, Simon Pieters wrote: In my testing this appears to not be the case. You're absolutely right. I missed a well-hidden early return, my apologies. -Boris

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Yoav Weiss
On Tue, Dec 17, 2013 at 5:06 PM, Boris Zbarsky wrote: > On 12/17/13 3:29 AM, Jonas Sicking wrote: > >> This is a good point. Would this have performance implications for >> down-level browsers? I don't know if prescanners etc in contemporary >> browsers are smart enough to ignore

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Yoav Weiss
On Tue, Dec 17, 2013 at 9:29 AM, Jonas Sicking wrote: > On Mon, Dec 9, 2013 at 1:33 AM, Yoav Weiss wrote: > >> > > or > >> > > something else. Like you said, I think it's a conversation we need > to > >> > > have with the HTML people. > >> > > >> > > >> > I’ll investigate a bit more. I’ve added

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Simon Pieters
On Wed, 18 Dec 2013 11:58:07 +0100, Simon Pieters wrote: On Tue, 17 Dec 2013 17:06:57 +0100, Boris Zbarsky wrote: On 12/17/13 3:29 AM, Jonas Sicking wrote: This is a good point. Would this have performance implications for down-level browsers? I don't know if prescanners etc in contempora

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-18 Thread Simon Pieters
On Tue, 17 Dec 2013 17:06:57 +0100, Boris Zbarsky wrote: On 12/17/13 3:29 AM, Jonas Sicking wrote: This is a good point. Would this have performance implications for down-level browsers? I don't know if prescanners etc in contemporary browsers are smart enough to ignore

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-17 Thread Boris Zbarsky
On 12/17/13 3:29 AM, Jonas Sicking wrote: This is a good point. Would this have performance implications for down-level browsers? I don't know if prescanners etc in contemporary browsers are smart enough to ignore

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-17 Thread Jonas Sicking
On Mon, Dec 9, 2013 at 1:33 AM, Yoav Weiss wrote: >> > > or >> > > something else. Like you said, I think it's a conversation we need to >> > > have with the HTML people. >> > >> > >> > I’ll investigate a bit more. I’ve added a bug here: >> > https://github.com/w3c/manifest/issues/91 >> > >> > I’l

Re: New manifest spec - ready for FPWD?

2013-12-16 Thread Marcos Caceres
On Monday, December 9, 2013 at 10:51 PM, Mounir Lamouri wrote: > On Wed, Dec 4, 2013, at 10:03, Marcos Caceres wrote: > > From the research we’ve done, none of the proprietary solutions currently > > do this. I’ve added this as a feature request [1] so we can see how much > > interest there is.

Re: New manifest spec - ready for FPWD?

2013-12-10 Thread Marcos Caceres
Hi Rob, On Wednesday, November 27, 2013 at 9:28 AM, Rob Manson wrote: > That's a great overview! > > There's 2 points I think haven't fully been addressed. > > 1. Section 8. Navigation > Much of this work (and HTML5 in general) is about bringing the Web > Platform up to being "equal" wit

Re: New manifest spec - ready for FPWD?

2013-12-10 Thread Marcos Caceres
On Wednesday, November 27, 2013 at 10:37 PM, Mounir Lamouri wrote: > On Wed, Nov 27, 2013, at 8:02, Marcos Caceres wrote: > > Over the last few weeks, a few of us folks in the Web Mob IG have been > > investigating the use cases and requirements for bookmarking web apps to > > home screen. The o

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Mounir Lamouri
On Mon, Dec 9, 2013, at 20:33, Yoav Weiss wrote: > IMO, it might be better not to define an explicit way to inline the > manifest, and let authors simply use data URIs to do that, if they see > such > a need. > e.g. > > If this becomes a common authoring pattern, an explicit mechanism might > be

Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Mounir Lamouri
On Wed, Dec 4, 2013, at 10:03, Marcos Caceres wrote: > From the research we’ve done, none of the proprietary solutions currently > do this. I’ve added this as a feature request [1] so we can see how much > interest there is. I think it is exaggerated to say that pages rely on the user seeing the

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Kornel Lesiński
On 9 December 2013 09:33:47 Yoav Weiss wrote: IMO, it might be better not to define an explicit way to inline the manifest, and let authors simply use data URIs to do that, if they see such a need. e.g. If this becomes a common authoring pattern, an explicit mechanism might be a good fit. Ot

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Yoav Weiss
On Wed, Dec 4, 2013 at 7:16 AM, Jonas Sicking wrote: > On Dec 3, 2013 9:25 PM, "Marcos Caceres" wrote: > > On Wednesday, December 4, 2013 at 9:40 AM, Jonas Sicking wrote: > > > We currently have both ... and , as > > > well as both and and