Hi Thomas,
Thank you for pushing feature policy over the finish line and making the web a
safer place!
Best
Nils Ohlmeier
> On 25Nov, 2019, at 04:41, Thomas Nguyen wrote:
>
> Summary: People don’t have a good understanding of iframes, because
> generally, no UI indicates that
in WebRTC together with TLS 1.0 and 1.1 in March
2020.
Disabling DTLS 1.0 is tracked at
https://bugzilla.mozilla.org/show_bug.cgi?id=1506392
<https://bugzilla.mozilla.org/show_bug.cgi?id=1506392>
Best
Nils Ohlmeier
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Wow. This is awesome. So much better then the old certificate viewer!
Thanks
Nils
> On 16Aug, 2019, at 12:52, Danielle Leblanc-Cyr
> wrote:
>
> Hi everyone,
>
> We’re Carolina and Danielle, two Outreachy interns who have been working
> with the Security Engineering team. We’ve spent the pas
it that I have not read your full description.
But I have not found any reference to the RIPE Atlas project
https://atlas.ripe.net/ <https://atlas.ripe.net/>
I think it would be worth checking what can be achieved with RIPE Atlas and
what is missing from that project in comparison to yours.
B
raising this to
clarify that WPT as of right now can not solved all existing problems.
Best
Nils Ohlmeier
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
As the Telemetry data [1] shows no significant usage of the DHE ciphers in Beta
63 and Nightly 64 we are planing to remove the DHE ciphers in Firefox 65.
Please voice your concerns now, if you have any.
Best
Nils Ohlmeier
[1]
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative
la.org/show_bug.cgi?id=1227519
<https://bugzilla.mozilla.org/show_bug.cgi?id=1227519>
Targeted release: Firefox 66
Best
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP
___
dev-platform mailing list
dev-platform@lists.mozil
Which version of Firefox are you planing to ship this?
Thanks
Nils
> On Aug 6, 2018, at 02:37, Jean-Yves Avenard wrote:
>
> Summary:
>
> enable by default changeType method on MediaSource’s Source Buffer, allowing
> to change content type (codecs and/or container) on the fly…
> The method h
iled into Firefox.
Since this discussion has reached pretty low levels of WebRTC it might be time
to move this conversation to dev-media, which has more expert subscribers then
this generic mailing list.
Best
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP
__
n, etc. That may complicate what you're doing.
>
> If you want to do more than personal/local experimentation, much more
> extensive discussions and work would be required.
If you are part of the IRTF research group and you are going to be at the
Montreal meeting it
ehind current
webrtc.org <http://webrtc.org/> (right now Firefox is at version 57).
Best
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Looks like the existing WebAudio issue
https://github.com/WebAudio/web-audio-api/issues/1471
<https://github.com/WebAudio/web-audio-api/issues/1471>
is where this should get resolved (for people who haven’t switched over there
yet).
Best regards
Nils Ohlmeier
> On May 2, 2018,
> On Aug 16, 2017, at 07:23, James Graham wrote:
>
> On 16/08/17 01:26, Nils Ohlmeier wrote:
>> I guess not a lot of people are aware of it, but for WebRTC we still have
>> two distinct implementations for the networking code.
>> So if I understand the impact h
I guess not a lot of people are aware of it, but for WebRTC we still have two
distinct implementations for the networking code.
So if I understand the impact here right we just lost test coverage for
probably a couple of thousand lines of code.
And yes you can potentially blame it on WebRTC netw
> On Mar 17, 2017, at 11:01, Boris Zbarsky wrote:
>
> We have tools for this: "mach wpt-manifest-update" will do the right thing.
>
> The typical result of hand-edits is that later changesets that do use the
> tools end up conflicting with each other, as they all fix up the incorrect
> hand-e
> On Jul 10, 2016, at 21:18, Xidorn Quan wrote:
>
> On Mon, Jul 11, 2016, at 12:29 PM, Martin Thomson wrote:
>> Is now the right time to start talking about retiring checkin-needed,
>> or is it still heavily used?
>
> Isn't it still necessary for people who don't yet have permission to
> push?
e DevEdition installed on the same system updated itself to 48. And 48
started and appeared to be still working.
Best
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
dev-platform mailing list
dev-platfor
Nightly 40 on 10.6.8 and it simply refused to do any
update at all. That is less then ideal I would say.
Best regards
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
> On Apr 18, 2016, at 09:56, Milan Sreckovic wrote:
>
> What’s the “XP tax”? Graphics usually tries to simplify the playing field as
> much as possible, but I can’t say that XP has been causing any trouble, or
> that we have been getting too many XP specific problems (certainly fewer than
>
but would be interested in the counter arguments for such a “middle
ground solution”.
Best regards
Nils Ohlmeier
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
dev-platform mailing list
dev-platform@lists.mozil
’t seem to be able to make my case here I’ll simply live with
requesting flaky timeouts for all WebRTC tests.
Best
Nils
> Cheers,
> Ehsan
>
> On 2014-12-19 1:07 AM, Boris Zbarsky wrote:
>> On 12/18/14, 2:28 PM, Nils Ohlmeier wrote:
>>> Well there is an event listener w
> On Dec 17, 2014, at 11:47 PM, Daniel Holbert wrote:
> In contrast, your scenario is:
> - We're expecting that an event *will* fire.
> - We wait a bit to see if it fires.
> - Fail if it the event *does not* fire before the timeout expires.
>
> Here, failures are iffy - they may or may not be "r
ery easily write a legit test case without ever calling setTimeout yourself,
but some of the generic helper code will do it for the test writer. And then
the current error message essentially means nothing to him.
Best
Nils Ohlmeier
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Thanks Jonathan for the update.
I would like to point out that at least for the WebRTC tests which do
test the connection between two WebRTC clients we theoretically also
have the option to split the tests into two half's (which we do for
steeplechase tests already anyhow), and then start two
24 matches
Mail list logo