Hi,
In bug 1535438 I intend to remove three Shadow DOM v0 APIs that slipped
through when we shipped Shadow DOM v1:
* ShadowRoot.getElementsByTagName
* ShadowRoot.getElementsByTagNameNS
* ShadowRoot.getElementsByClassName
These were implemented in bug 806506 as part of the initial Shadow DOM
A W3C Proposed Recommendation is available for the membership of
W3C (including Mozilla) to vote on, before it proceeds to the final
stage of being a W3C Recomendation:
Pointer Events Level 2
https://www.w3.org/TR/pointerevents2/
https://w3c.github.io/pointerevents/
Deadline for
I am not worried about this potential problem.
It doesn't have to be perfect, some folks (release managers, qa, etc) will
check that the values are correctly set.
In parallel, you probably noticed that we have a bot (autonag) which
automatically set/update a bunch of values.
@Felipe: yeah, the
On Fri, Mar 15, 2019 at 4:47 PM J.C. Jones wrote:
> That's a good argument for us never "optimizing" it to avoid re-downloading
> already-known certs. Just download the whole set once, everywhere - the
> bandwidth savings are limited.
Yes and No. As ekr pointed out to me offline, there are so
On Thu, Mar 14, 2019 at 3:26 PM Nicholas Alexander
wrote:
> J.C. -- I don't think this answers Tom's question, but perhaps it does. In
> that case I'll ask what I think is the same question:
Actually, what I was worried about was Mozilla being able to track
users based on what the client
On 15/03/2019 14:31, Xidorn Quan wrote:
Servo has a policy banning duplicate dependencies with a whitelist,
and such list currently has:
This exact allow-list is not part of Servo’s policy, but is constantly
evolving. If you can reduce it (typically by updating some intermediate
dependencies
On Fri, Mar 15, 2019 at 11:35 AM Tom Ritter wrote:
> Thanks for more details on the use case.
>
> On Wed, Mar 6, 2019 at 1:35 AM wrote:
> >
> > On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> > > To add to Dan's comments here...
> > >
> > > Assuming that I'm reading
On Fri, Mar 15, 2019, 15:39 Andreas Tolfsen wrote:
> However, I want to talk a little bit about _why_ we see so many
> duplicate crates and what causes it. It is my experience that far
> too many dependencies are defined on exact version numbers, e.g.
> "log = 0.3.9", which effectively forces
Thanks for more details on the use case.
On Wed, Mar 6, 2019 at 1:35 AM wrote:
>
> On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> > To add to Dan's comments here...
> >
> > Assuming that I'm reading this correctly [1], the fingerprinting risks are
> > pretty extreme
Also sprach Xidorn Quan:
> Should we have some kind of policy to address duplicate dependencies
> in Gecko as well? Maybe I'm missing something but I don't think I'm
> aware of any previous discussion about this.
Deduplicating crate dependencies has so far been a mostly heroic
undertaking done
Hello
Yes, it will be the same as block/depend in term of notification.
Sylvestre
Le 12/03/2019 à 19:12, David Major a écrit :
Will setting the "regressed by" field send mail to the subscribers of
the earlier bug? This was a useful aspect of the blocks/depends field.
On Tue, Mar 12, 2019 at
On Fri, Mar 15, 2019 at 9:32 AM Xidorn Quan wrote:
> Should we have some kind of policy to address duplicate dependencies in Gecko
> as well? Maybe I'm missing something but I don't think I'm aware of any
> previous discussion about this.
I remember IRC discussions about this, but there were
A short PSA about MOZ_LOG() messages:
In Bug 1518030 back in January, I landed support for mirroring MOZ_LOG()
messages into profiles captured with the Gecko Profiler
(https://profiler.firefox.com/ formerly https://perf-html.io/).
You can now add "profilermarkers" to you MOZ_LOG env variable to
FWIW there often ad-hoc attempts to deduplicate Rust dependencies, and
they often run into nontrivial blockers. Currently there's a few
things blocked on bug 1530448.
On Fri, Mar 15, 2019 at 9:32 AM Xidorn Quan wrote:
>
> Hi all,
>
> Recently I tried to build Firefox on cloud, and noticed that
Hi all,
Recently I tried to build Firefox on cloud, and noticed that building Rust
dependencies is now a significant part of it. Another thing I noticed is that,
we have lots of duplicate Rust dependencies.
I scanned Cargo.lock in the root and found that we have:
* 2 versions of block-buffer
Hello Mozilla developers,
As some of you may know, Igalia is working on MathML support in Chromium
this year [1]. As part of that effort we joined a new MathML Refresh
Community Group [2] and one goal is to focus on a core spec for browser
implementations [3] to:
- Remove
16 matches
Mail list logo
