Background: RTCRtpReceiver's[1] getSynchronizationSources() method
allows WebRTC applications to monitor volume levels of call participants
without having to use the costly getStats()[2] call. RTCRtpReceiver's
getContributingSources() method enables WebRTC applications to monitor
the volume lev
Yes!
Thank you for bringing it up. I forgot to mention it in my original message.
We also removed `intl.locale.matchOS` and turned an empty
`intl.locale.requested` to mean "use OS locales" [0].
zb.
[0]
https://hg.mozilla.org/integration/autoland/file/tip/intl/locale/LocaleService.cpp#l75
On Tue
On Tue, Dec 05, 2017 at 03:15:06PM -0800, Zibi Braniecki (Gandalf) wrote:
> Hi all,
>
> We just landed a major patch which replaces `general.useragent.locale` pref
> with a new pref `intl.locale.requested`.
>
> Historically, `general.useragent.locale` has been widely used to set a
> locale for Fi
Hi all,
We just landed a major patch which replaces `general.useragent.locale` pref
with a new pref `intl.locale.requested`.
Historically, `general.useragent.locale` has been widely used to set a
locale for Firefox UI.
This year, we introduced a full new API called mozilla::intl::LocaleService
w
On Tue, Dec 05, 2017 at 05:16:52PM +0200, Henri Sivonen wrote:
> On Tue, Dec 5, 2017 at 4:37 PM, ISHIKAWA,chiaki wrote:
> > There are other non-ASCII character issues such as
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
>
> Very weird bug! (Summary for others: decomposed voiced sound
On Wed, Dec 6, 2017, at 01:25 AM, Dragana Damjanovic wrote:
> Hi all,
>
> We have implemented this for a log time, but the pref was turned off.
> I intend to switch on the pref for this in bug 1423146.
> After the pref is switched a http-authentication dialog prompt will not
> be
> shown if it is
devices initially, with other transports and FIDO 2.0 device support
to follow in 2018.
Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=webauthn
Spec: https://www.w3.org/TR/webauthn/
(Note that the latest working draft,
https://www.w3.org/TR/2017/WD-webauthn-20171205/, is considered by
On 2017/12/06 1:04, Jonathan Kew wrote:
On 05/12/2017 15:16, Henri Sivonen wrote:
On Tue, Dec 5, 2017 at 4:37 PM, ISHIKAWA,chiaki
wrote:
There are other non-ASCII character issues such as
https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
Very weird bug! (Summary for others: decomposed voi
As a follow-up, it looks like updating to a newer LLVM version fixes the
problem. That update is being tracked in
https://bugzilla.mozilla.org/show_bug.cgi?id=1423307.
For anybody already hitting this bustage locally, you can try updating your
clang toolchain under ~/.mozbuild/clang to the one bel
There are also various Firefox extensions that can manage 2 factor accounts
for you.
On Tue, Dec 5, 2017 at 3:10 PM, Byron Jones wrote:
> TOTP does not require a smartphone.
>
> there's software TOTP clients that can be run on your desktop, and i'm
> also seeing TOTP support baked into some pass
On Tue, Dec 5, 2017 at 9:16 AM, Emilio Cobos Álvarez
wrote:
> That looks like bindgen, but the error is a C++ one, that is, it's clang
> who is choking to parse type_traits. Which version of libclang is this
> using?
>
The libclang version supplied to bindgen is set by
https://searchfox.org/moz
On 12/05/2017 05:16 PM, Ryan VanderMeulen wrote:
> FYI, the VC++ 2017 v14.12 toolset included in the recently-released VS2017
> 15.5 update appears to have broken building Firefox due to issues with the
> Rust compiler (in particular, the version of libclang we ship with it) and
> one of the system
FYI, the VC++ 2017 v14.12 toolset included in the recently-released VS2017
15.5 update appears to have broken building Firefox due to issues with the
Rust compiler (in particular, the version of libclang we ship with it) and
one of the system headers:
C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MS
On 05/12/2017 15:16, Henri Sivonen wrote:
On Tue, Dec 5, 2017 at 4:37 PM, ISHIKAWA,chiaki wrote:
There are other non-ASCII character issues such as
https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
Very weird bug! (Summary for others: decomposed voiced sound mark is
rendered on the wrong b
On Tue, Dec 5, 2017 at 4:37 PM, ISHIKAWA,chiaki wrote:
> There are other non-ASCII character issues such as
> https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
Very weird bug! (Summary for others: decomposed voiced sound mark is
rendered on the wrong base character.)
> But the bug I mention o
On 2017/12/05 22:24, Henri Sivonen wrote:
On Mon, Dec 4, 2017 at 2:04 PM, Masatoshi Kimura wrote:
* If by any chance a profile path contains non-ASCII characters on
non-UTF-8 UNIX systems, Firefox 57.0.1 must have broken the profile just
like 57.0 broke it on Windows. But we didn't hear any suc
On Tue, Dec 5, 2017 at 3:24 PM, Henri Sivonen wrote:
> On Mon, Dec 4, 2017 at 2:04 PM, Masatoshi Kimura wrote:
>> * If by any chance a profile path contains non-ASCII characters on
>> non-UTF-8 UNIX systems, Firefox 57.0.1 must have broken the profile just
>> like 57.0 broke it on Windows. But we
Hi all,
We have implemented this for a log time, but the pref was turned off.
I intend to switch on the pref for this in bug 1423146.
After the pref is switched a http-authentication dialog prompt will not be
shown if it is triggered by an image resource from a cross-origin.
Chrome already was th
TOTP does not require a smartphone.
there's software TOTP clients that can be run on your desktop, and i'm
also seeing TOTP support baked into some password managers. that
clearly isn't as secure as the second factor implemented on a second
device, however desktop TOTP does provide better sec
On Tue, Dec 5, 2017 at 2:38 PM, Masatoshi Kimura
wrote:
> I went to the 2FA preference on BMO. For me, the only authentication
> option was TOTP that requires a smartphone. I do not have a smartphone
> like Mark.
>
TOTP doesn't require a smartphone at all, even though that is how many
people use
> On Dec 5, 2017, at 08:38, Masatoshi Kimura wrote:
>
> I went to the 2FA preference on BMO. For me, the only authentication
> option was TOTP that requires a smartphone. I do not have a smartphone
> like Mark.
There are TOTP programs for non-mobile OSes as well.
See
https://superuser.com/ques
I went to the 2FA preference on BMO. For me, the only authentication
option was TOTP that requires a smartphone. I do not have a smartphone
like Mark.
How can I continue to contribute after we are forced to use Phabricator?
Mozilla no longer wants volunteer contributors?
On 2017/11/30 3:05, Mark
On Mon, Dec 4, 2017 at 2:04 PM, Masatoshi Kimura wrote:
> * If by any chance a profile path contains non-ASCII characters on
> non-UTF-8 UNIX systems, Firefox 57.0.1 must have broken the profile just
> like 57.0 broke it on Windows. But we didn't hear any such complaints.
Are you referring to
htt
Excellent! I won't miss it :)
On 05.12.2017 08:25, Brian Birtles wrote:
> Background: SMIL includes a feature for triggering animations based on
> keypresses:
>
> e.g.
>
>
>
>
>
> Proposal: In bug 1423098 I intend to remove this feature.
>
> Rationale:
>
> * Apart from Gecko,
On Tue, Dec 5, 2017 at 3:00 AM, Gregory Szorc wrote:
> My understanding from contributing to Mercurial (version control tools are
> essentially virtual filesystems that need to store paths and realize them
> on multiple operating systems and filesystems) is as follows.
When writing system tools t
25 matches
Mail list logo
