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: Passsword managers and autocomplete='off'

2013-12-18 Thread Joel Weinberger
On Wed, Dec 18, 2013 at 8:09 AM, Jonathan Bond-Caron < jbo...@gdesolutions.com> wrote: > > On the other hand, if all browsers collectively chose to completely > > ignore autocomplete=off, that might allow proceeding more > > aggressively. > > Sure, and that's why we're bringing it up with th

RE: Passsword managers and autocomplete='off'

2013-12-18 Thread Jonathan Bond-Caron
> On the other hand, if all browsers collectively chose to completely > ignore autocomplete=off, that might allow proceeding more > aggressively. > Sure, and that's why we're bringing it up with the > standards body. Before we proceed any further, we want to make sure that > (a) our intention

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: CfC: publish Candidate Recommendation of File API; deadline November 28

2013-12-18 Thread Arthur Barstow
On 12/2/13 3:30 PM, ext Arun Ranganathan wrote: On Dec 1, 2013, at 10:24 AM, Arthur Barstow wrote: Since this CfC was started, Arun reopened [23853] on November 28 and [23946] was filed on November 30. Arun - what's the plan here vis-à-vis this CfC? -Thanks, ArtB [23853]

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

[pointerlock] Call for Implementations and Tests

2013-12-18 Thread Arthur Barstow
[ Bcc public-webapps-testsuite ] Hi All, On December 17 a Candidate Recommendation of Pointer Lock was published and that triggered a Call for Implementations: Congratulations to Vincent (who also agreed to be the spec's Test Facilitato

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