If it's useful as a data point, in Gecko we used not to care about
non-unified builds. This worked kind of ok, because the file
arrangements were mostly deterministic by directory. However, folks
running with weird build configurations always ended up hitting these
issues (and they might not
boxes)
could solve.
-- Emilio
On 2/23/21 22:08, Emilio Cobos Álvarez via webkit-dev wrote:
Just thinking out loud, but has an environment variable for scrollbar
widths (maybe two, one for thin scrollbars, one for regular-width
scrollbars) be enough to do the job here?
I recall similar
Just thinking out loud, but has an environment variable for scrollbar
widths (maybe two, one for thin scrollbars, one for regular-width
scrollbars) be enough to do the job here?
I recall similar proposals in the CSSWG, but I'm not sure if they were
discussed seriously. It seems it should be
Interesting. This looks fairly similar to some of the checkers we use in
mozilla-central, fwiw.
One interesting difference is that we opted for explicitly annotating
the functions that can run script (think updateStyleIfNeeded(),
dispatchEvent() etc equivalents) to be able to not warn for
on crbug.com/920289 <http://crbug.com/920289>. Let's
discuss there.
On Tue, Oct 29, 2019 at 3:03 PM Emilio Cobos Álvarez <mailto:emi...@mozilla.com>> wrote:
Hi all,
10/18/19 7:19 PM, Chris Harrelson wrote:
> Hi,
>
> Another quick update: Emi
Hi all,
10/18/19 7:19 PM, Chris Harrelson wrote:
Hi,
Another quick update: Emilio, Navid, Nick, Stefan and I met today and
discussed which issues are important to fix and why. We now have a list of
spec issues, and WPT tests to fix that are Chromium bugs, that should
substantially improve
On 9/29/19 5:07 AM, Rick Byers wrote:
On Fri, Sep 27, 2019 at 10:16 AM Emilio Cobos Álvarez
mailto:emi...@mozilla.com>> wrote:
Hi Steve,
On 9/27/19 4:03 PM, Steve Kobes wrote:
> Hi Emilio,
>
> My recollection is that scroll anchoring was, in fact, a
issues for our
reasoning behind these changes, which I think would apply to Chrome as
well).
-- Emilio
On Fri, 27 Sep 2019 at 09:09, Emilio Cobos Álvarez <mailto:emi...@mozilla.com>> wrote:
And, to be clear, we _can_ fix these compat issues, some way or another.
One thought is
the
user dispatches, the timing of these events relative to other events, etc...
-- Emilio
[1]:
https://docs.google.com/document/d/1nQAO4MYCDMn0rTkn_-WI6gjumk3Qi2Bn-MGuB3NlVxE/edit
On 9/27/19 2:23 PM, Emilio Cobos Álvarez wrote:
Hi,
(cc'ing webkit-dev@ and blink-dev@ in case they have feedback or
Hi,
(cc'ing webkit-dev@ and blink-dev@ in case they have feedback or
opinions, as WebKit is the only engine which does not implement scroll
anchoring, though I don't know if they plan to, and Blink is the only
other engine that does implement it. Please reply to dev-platform@ though.)
TLDR:
On 19/03/2019 00:56, Michael Catanzaro wrote:
> On Mon, Mar 18, 2019 at 4:43 PM, Andy Estes wrote:
>> FWIW, Apple’s ports use the equivalent clang warning for pessimizing
>> and redundant moves, and we cleaned up a bunch of these mistakes in
>> our ports a few years ago. Hopefully you aren’t
On 10/12/18 3:59 AM, Geoffrey Garen wrote:
Honest question: What’s gross about using @font-face?
It would be lots of test edits. That’s a bummer.
But maybe it’s clearer for the tests to specify the font they want to use. It
makes the test self-describing, eliminating the requirement that the
12 matches
Mail list logo
