The W3C is proposing a revised charter for:
Second Screen Presentation Working Group
http://lists.w3.org/Archives/Public/public-new-work/2014Jul/0001.html
http://www.w3.org/2014/secondscreen/charter-draft.html
deadline for comments: September 12 (this Friday!)
Mozilla has the opportunity
Which version are we thinking of enabling this for? For Gecko
34/FirefoxOS 2.1 or a later version?
On Wed, Sep 3, 2014 at 10:36 AM, Tim Taubert wrote:
> As of September we intend to enable the WebCrypto API by default on all
> platforms. It has been developed behind the dom.webcrypto.enabled
> pr
On Tue, Sep 9, 2014 at 1:32 AM, Henri Sivonen wrote:
> On Mon, Sep 8, 2014 at 6:06 PM, Eric Rescorla wrote:
> > On Sun, Sep 7, 2014 at 11:45 PM, Henri Sivonen
> wrote:
> >> On Fri, Sep 5, 2014 at 4:15 PM, Eric Rescorla wrote:
> >> > On Fri, Sep 5, 2014 at 3:34 AM, Henri Sivonen
> >> > wrote:
On Tue, Sep 9, 2014 at 12:22 PM, Mounir Lamouri wrote:
> On Tue, 9 Sep 2014, at 00:15, Lars Knudsen wrote:
> > looks good,
> >
> > maybe adding to always take a holistic view on what you are doing and how
> > it will interact with other specs/standards used in the same apps (e.g.
> > considering
On 2014-09-09, 8:44 AM, James Graham wrote:
On 08/09/14 19:42, Ehsan Akhgari wrote:
I think unreviewed tests should still be run by browsers' automated
testing framework (obviously unless they take too long, are
unreliable, etc.). They just shouldn't be counted toward any claims
of conformance.
On 2014-09-09, 7:25 AM, Anne van Kesteren wrote:
On Tue, Sep 9, 2014 at 12:48 PM, Tim Taubert wrote:
Completely agree with Ehsan and Henri. I don't know of any plans to even
consider doing that and we currently expose the WebCrypto API to
unauthenticated origins as well.
Note https://www.w3.o
On 2014-09-09, 6:35 AM, Tim Taubert wrote:
Ehsan Akhgari wrote:
Can you please clarify what are the areas that we don't fully adhere to
the spec? Do we expect the fixes to those and potentially new spec
issues in the future to break backwards compatibility?
KeyAlgorithms were recently changed
On 9/9/14, 2:57 AM, Kilik kuo wrote:
Boris Zbarsky於 2014年9月8日星期一UTC+8下午11時51分04秒寫道：
boolean available;
This needs a default value.
I'm not quite sure about this,
I am. ;)
Since it's an optional argument for AvailableChangeEvent.
Right, and the question is: what is the behavior whe
On 9/9/2014 5:38 AM, Tim Taubert wrote:
helpcrypto helpcrypto wrote:
I'll love to know if Mozilla/Firefox is going to provide something (even
out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
The WebCrypto API basically exposes PKCS#11/NSS functionality with a DOM
API.
The c
On 08/09/14 19:42, Ehsan Akhgari wrote:
>> I think unreviewed tests should still be run by browsers' automated
>> testing framework (obviously unless they take too long, are
>> unreliable, etc.). They just shouldn't be counted toward any claims
>> of conformance. Even if the expected values are e
Thanks for your answers, Tim.
On Tue, Sep 9, 2014 at 12:38 PM, Tim Taubert wrote:
> helpcrypto helpcrypto wrote:
> > I'll love to know if Mozilla/Firefox is going to provide something (even
> > out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
>
> The WebCrypto API basically ex
On Tue, Sep 9, 2014 at 12:48 PM, Tim Taubert wrote:
> Completely agree with Ehsan and Henri. I don't know of any plans to even
> consider doing that and we currently expose the WebCrypto API to
> unauthenticated origins as well.
Note https://www.w3.org/Bugs/Public/show_bug.cgi?id=25972 which I
fi
Anne van Kesteren wrote:
> In Chromium the methods only work on authenticated origins. What is
> our story?
Completely agree with Ehsan and Henri. I don't know of any plans to even
consider doing that and we currently expose the WebCrypto API to
unauthenticated origins as well.
> Is the non-overl
Dirkjan Ochtman wrote:
> Is there a list of algorithms we support somewhere, particularly the
> ones we share with Chromium? IIRC the supported algorithms is where
> the real interop problems are expected to be. (I quickly searched MDN,
> but that didn't turn up anything useful.)
Richard Barnes ma
On Tue, Sep 9, 2014 at 1:26 PM, Mounir Lamouri wrote:
> On Tue, 9 Sep 2014, at 10:10, Daniel Veditz wrote:
>> On 9/8/2014 2:16 AM, Mounir Lamouri wrote:
>> > On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
>> >> It's more the case that a persistent positive grant from permission
>> >> manager
helpcrypto helpcrypto wrote:
> I'll love to know if Mozilla/Firefox is going to provide something (even
> out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
The WebCrypto API basically exposes PKCS#11/NSS functionality with a DOM
API.
> This will fill the gap that currently exist
On Mon, Sep 8, 2014 at 7:10 PM, Martin Thomson wrote:
> Don't look at me. My assessment is that this isn't superb, but it's not a
> hill worth dying on. You are welcome to disagree, of course:
> public-media-capt...@w3.org
http://lists.w3.org/Archives/Public/public-media-capture/2014Sep/0013.ht
Ehsan Akhgari wrote:
> Can you please clarify what are the areas that we don't fully adhere to
> the spec? Do we expect the fixes to those and potentially new spec
> issues in the future to break backwards compatibility?
KeyAlgorithms were recently changed to dictionaries (from interfaces)
and we
On Tue, 9 Sep 2014, at 10:10, Daniel Veditz wrote:
> On 9/8/2014 2:16 AM, Mounir Lamouri wrote:
> > On Sun, 7 Sep 2014, at 04:56, Martin Thomson wrote:
> >> It's more the case that a persistent positive grant from permission
> >> manager would be ignored for non-secure origins and non-secure origin
On Tue, 9 Sep 2014, at 00:15, Lars Knudsen wrote:
> looks good,
>
> maybe adding to always take a holistic view on what you are doing and how
> it will interact with other specs/standards used in the same apps (e.g.
> considering DeviceOrientation and DeviceMotion before makeing
> OrientationLock
On Mon, Sep 8, 2014 at 6:06 PM, Eric Rescorla wrote:
> On Sun, Sep 7, 2014 at 11:45 PM, Henri Sivonen wrote:
>> On Fri, Sep 5, 2014 at 4:15 PM, Eric Rescorla wrote:
>> > On Fri, Sep 5, 2014 at 3:34 AM, Henri Sivonen
>> > wrote:
>> >> On Fri, Sep 5, 2014 at 1:25 PM, Robert O'Callahan
>> >>
>> >
Boris Zbarsky於 2014年9月8日星期一UTC+8下午11時51分04秒寫道：
> >> dictionary AvailableChangeEventInit : EventInit {
>
> >>boolean available;
>
>
>
> This needs a default value.
I'm not quite sure about this,
Since it's an optional argument for AvailableChangeEvent.
I assume it would be used in the scena
22 matches
Mail list logo
