My gut tells me that there would be fallout with users. I've been personally
told by more than one user that they are unwilling to use browsers without it,
as they feel like user-unfriendly relics.
As such I would recommend not removing it unless Blink does. I suspect that if
we can handle the
On Monday, April 9, 2018 at 11:39:35 AM UTC-4, Henri Sivonen wrote:
> How do I waive .cargo-checksum.json checking for a crate?
In bug 1449613 (part 12) I just hand-edited the .cargo-checksum.json in
question, and updated the sha256 values for the modified files. That was enough
to get try runs
On Tuesday, March 27, 2018 at 4:38:56 PM UTC-4, Emilio Cobos Álvarez wrote:
> That looks like an easy fix though, I'll ensure it gets fixed before
> landing. Filed bug 1449010.
If it helps, I had a patchset for this in bug 292563, but ran into an odd
reftest failure that I never had time to
> Will those measures be part of the work done (enabled only when
> privacy.resistFingerprinting is set)?
If we want them to be, sure. I don't mind adding a patch to do so as part of
the initial landing rather than a follow-up.
Bear in mind that I'm operating on the presumption that we would
4 matches
Mail list logo
