Re: What to do about scroll anchoring?
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 compat fallout, we should document well our heuristics and try to standardize them properly. Blink should at least agree to that much if they want to push the notion, and it does seem worthy of that much effort if users truly are that invested. I suspect that if we can give our compat addon an easy way to specify sites which need an opt-out, that might ease the pain. Likewise, as obnoxious as the thought is, perhaps giving sites a standard way to opt out of anchoring could be a reasonable compromise, depending on developer feedback. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Editing a vendored crate for a try push
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 going (though the debug builds do show related failures, they still built and ran my tests). ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to unprefix: ::-moz-selection.
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 figure out. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to implement: CSS media queries, interaction media features
> 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 want anti-fingerprinting to always return values for Windows/OSX/Linux that convey there is only a fine, hover-capable pointer (a mouse), and on Android to convey that there is only a coarse, non-hover-capable pointer (a touchscreen). If that's not good, then please let me know. >Note that the system metric media queries respond to the privacy.resistFingerprinting pref. I think we should keep doing the same for this one. Agreed. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
