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 a bug here:
> >> > https://github.com/w3c/manifest/issues/91
> >> >
> >> > I’ll just note that having  and 
> >> > manifest would kinda suck… if we can just have:
> >> >
> >> > *