Re: [desktop] Bugs logged by Desktop Release QA in the last 8 days

On Monday, May 14, 2018 at 12:26:01 PM UTC+5:30, Bogdan Maris wrote: > Hello, > > Here's the list of new issues found and filed by the Desktop Release QA team > last week. > Additional details on the team's priorities last week, as well as the plans > for the current week are available at: https

Re: PSA: Avoid Visual Studio 2017 15.7.0

On Tuesday, May 8, 2018 at 7:10:47 PM UTC+5:30, Ryan VanderMeulen wrote: > Yesterday, Microsoft released Visual Studio 2017 15.7.0. Unfortunately, it > is currently not usable for building Firefox due to bug 1458247 (internal > compiler errors in WebRTC code). The bug was already reported and confi

Re: Intent to ship: OpenType Variation Font support

On Tuesday, March 20, 2018 at 4:02:42 AM UTC+5:30, Jonathan Kew wrote: > As of this week, for the mozilla-61 cycle, I plan to turn support for > OpenType Font Variations on by default. > > It has been developed behind the layout.css.font-variations.enabled and > gfx.downloadable_fonts.keep_varia

Re: modifying vendored Rust crates locally

On Tue, May 15, 2018, at 8:22 AM, Myk Melez wrote: > With the fixes for bug 1323557 [1] and cargo-vendor issue #71 [2], it's > now more straightforward to modify a vendored Rust crate to test changes > locally or on tryserver. That is great! Thank you for making this easier, Myk. __

modifying vendored Rust crates locally

With the fixes for bug 1323557 [1] and cargo-vendor issue #71 [2], it's now more straightforward to modify a vendored Rust crate to test changes locally or on tryserver. To do so, specify the crate's vendored path in the [patch.crates-io] section of the top-level Cargo.toml file. For example

Re: Intent to ship: media-capabilities

On 5/14/18 3:18 PM, Jean-Yves Avenard wrote: The most obvious choice considered was to provide identical information to what the existing canPlayType information provide: that is not providing extra details. OK. All I'm saying is that this needs to be sorted out before we ship. I would inv

Re: Intent to ship: media-capabilities

> > On 14 May 2018, at 6:47 pm, Tom Ritter wrote: > > > > It seems like this will reveal a lot of information about the user's > > hardware. Does the Resist Fingerprinting preference disable the API or > > report standardized results? If not, can we get that bug on file (and > > if it's easy, poin

Intent to implement: Async Clipboard API

In about a week, my intern will be starting. As an initial project, I intend for her to implement the Async Clipboard API. Summary: The Async Clipboard API provides a more modern and performant interface to the user's clipboard. This API is intended to replace many consumers of the existing `docum

Re: Update on rustc/clang goodness

We've confirmed that this issue with debug symbols comes from lld-link and not from clang-cl. This will likely need a fix from the LLVM side, but in the meantime I'd like to encourage people not to be deterred from using clang-cl as your compiler. On Thu, May 10, 2018 at 9:12 PM Xidorn Quan wrote

Re: Intent to ship: media-capabilities

On Mon, May 14, 2018 at 1:57 PM, Jean-Yves Avenard wrote: > Hi > >> On 14 May 2018, at 6:47 pm, Tom Ritter wrote: >> >> It seems like this will reveal a lot of information about the user's >> hardware. Does the Resist Fingerprinting preference disable the API or >> report standardized results? If

Re: Intent to ship: media-capabilities

Hi > On 14 May 2018, at 6:53 pm, Boris Zbarsky wrote: > > On 5/14/18 11:19 AM, Jean-Yves Avenard wrote: >> The proposed spec is available at https://wicg.github.io/media-capabilities/ >> > > I have some questions about this spec and our implementati

Re: Intent to ship: media-capabilities

Hi > On 14 May 2018, at 6:47 pm, Tom Ritter wrote: > > It seems like this will reveal a lot of information about the user's > hardware. Does the Resist Fingerprinting preference disable the API or > report standardized results? If not, can we get that bug on file (and > if it's easy, point out e

Re: Intent to ship: media-capabilities

On 5/14/18 11:19 AM, Jean-Yves Avenard wrote: The proposed spec is available at https://wicg.github.io/media-capabilities/ I have some questions about this spec and our implementation: 1) What are the fingerprinting implications? What effect, if

Re: Intent to ship: media-capabilities

It seems like this will reveal a lot of information about the user's hardware. Does the Resist Fingerprinting preference disable the API or report standardized results? If not, can we get that bug on file (and if it's easy, point out exactly where we would want to add the 'if() return false'?) -to

Re: Intent to ship: media-capabilities

On 14/05/2018 16:19, Jean-Yves Avenard wrote: Media Capabilities allow for web sites to better determine what content to serve to the end user. Currently a media element offers the canPlayType method (https://html.spec.whatwg.org/multipage/media.html#dom-navigator-canplaytype-dev

Intent to ship: media-capabilities

Media Capabilities allow for web sites to better determine what content to serve to the end user. Currently a media element offers the canPlayType method (https://html.spec.whatwg.org/multipage/media.html#dom-navigator-canplaytype-dev

Re: Intent to ship: OpenType Variation Font support

On 13/05/2018 14:01, rosesharon...@gmail.com wrote: On Monday, March 19, 2018 at 3:32:42 PM UTC-7, Jonathan Kew wrote: As of this week, for the mozilla-61 cycle, I plan to turn support for OpenType Font Variations on by default. It has been developed behind the layout.css.font-variations.enable