Re: Proposed W3C Charters: Web Platform and Timed Media Working Groups

2015-09-08 Thread Jonas Sicking
On Tue, Sep 8, 2015 at 5:33 PM, Tantek Çelik wrote: > On Wed, Aug 19, 2015 at 3:16 AM, Henri Sivonen wrote: >> On Sun, Aug 9, 2015 at 9:59 PM, L. David Baron wrote: >> > The W3C is proposing revised charters for: >> > >> > Web Platform Working Group: >> > http://www.w3.org/2015/07/web-platfo

Re: Proposed W3C Charters: Web Platform and Timed Media Working Groups

2015-09-08 Thread Tantek Çelik
Follow-up on this, since we now have two days remaining to respond to these proposed charters. If you still have strong opinions about the proposed Web Platform and Timed Media Working Groups charters, please reply within 24 hours so we have the opportunity to integrate your opinions into Mozilla'

Update your custom Telemetry dashes: telemetry.js is obsolete

2015-09-08 Thread Vladan D
If you built a custom dashboard and used telemetry.js [1] to query telemetry.mozilla.org for histogram data, you'll need to switch your dash to a newer library -- either the new telemetry.js library [2] (preferred option) or our shim library [3]. This change is necessary because Telemetry is re

Re: Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Johnny Stenback
While deciding how much resources are available to complex applications is far from an easy task, and one for which there's no obvious best answer, at least not yet, I agree that giving developers this bit of information is critical to enable exploring this space and bring out the any remaining iss

Re: Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Ben Kelly
FWIW, I also think we should implement this. The clamping seems like a reasonable way to be conservative given the fingerprinting concerns. On Tue, Sep 8, 2015 at 3:21 PM, Luke Wagner wrote: > Since the original m.d.p thread on hardwareConcurrency last year: > > https://groups.google.com/d/topi

Re: Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Rik Cabanier
On Tue, Sep 8, 2015 at 2:14 PM, Robert O'Callahan wrote: > Yes, I think we should do this. > Happy to hear the positive responses. I implemented a patch for this last year. Since the code is trivial, it probably still applies: https://bugzilla.mozilla.org/show_bug.cgi?id=1008453

Re: Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Robert O'Callahan
Yes, I think we should do this. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodv

Re: Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Jonas Sicking
I'm ok with implementing this. My biggest concern has always been fingerprinting, and I think that we'll need some way to deal with active (i.e. client-side) fingerprinting anyway, so I don't think this makes a big difference either way. / Jonas On Tue, Sep 8, 2015 at 12:21 PM, Luke Wagner wrote

Proposal: revisit and implement navigator.hardwareConcurrency

2015-09-08 Thread Luke Wagner
Since the original m.d.p thread on hardwareConcurrency last year: https://groups.google.com/d/topic/mozilla.dev.platform/QnhfUVw9jCI/discussion the landscape has shifted (as always) and I think we should reevaluate and implement this feature. What hasn't changed are the arguments, made in the or

Re: StructuredCloneHelper

2015-09-08 Thread Bobby Holley
Awesome, thanks for working to unify this stuff baku! Can this stuff be applied to StackScopedClone (used by Cu.cloneInto etc), which currently does this stuff manually in ExportHelpers.cpp? On Fri, Sep 4, 2015 at 1:12 AM, Andrea Marchesini wrote: > Hi all, > > In these days I landed quite a fe

x-x509-*-cert - Re: On the future of and application/x-x509-*-cert MIME handling

2015-09-08 Thread Henry Story
> On 4 Sep 2015, at 22:43, Martin Thomson wrote: > > Henry, I would rather you attempt to address Ryan's point 5, namely: > > 5) just generates keys, and relies on > application/x-x509-*-cert to install certificates. This MIME handling, > unspecified but implemented by major browsers, represen