This will require that entries for renamed files be updated so that they don't
accidentally start being loaded under the new name later. It also prevents
dead code entries from sticking around after their targets are removed.
Using `throttledMapPromises` is probably not strictly necessary given the
small number of entries in most lists, but since it already exists, we may as
well use it here.
Differential Revision: https://phabricator.services.mozilla.com/D150921
I'm not including the testcase because it ends up being very slow in debug builds (because we're inserting thousands of shape assertions). The same testcase is fast in an opt build, so it doesn't seem worth pursuing.
Differential Revision: https://phabricator.services.mozilla.com/D150307
This fixes websites using jakearchibald/idb@v3 which has been downloaded 1 million times in NPM (https://www.npmjs.com/package/idb).
The library creates proxies for those interfaces while assuming those are always globally available, and we get an `undefined identifier` error if those don't exist.
Only the version 3 is affected and v4+ is okay per my testing, but v3 is downloaded too many times to ignore.
Differential Revision: https://phabricator.services.mozilla.com/D151086
da -> 2e7f937e2f8409ba8525986b7a08798aaf0e0b27
fi -> 433270def265c15f1c0c082148ccf20fc2113384
hu -> d6795607a4a80bf666b34cc18c72562423303ae8
it -> 81b12d188498fa459307bc06a9124f476381f3ee
kk -> 730a8e96f01684eedce7db0995a0cdd18b8e2314
nl -> d530826100a72d7a7ef622903ea5e3a3fa880e9c
tg -> 87925c0e1a4133b5c1070057a5513a8c33ca7174
tr -> 24179e96c206916f15ee475e7de00a26257ff63a
The old code in AddFloat() used to call nsBlockFrame::ComputeFloatISize() to
compute a float's inline-size, compare it with current line's available
inline-size, and determine whether FlowAndPlaceFloat() should be called.
However, it doesn't handle an orthogonal float with an auto block-size.
Luckily, FlowAndPlaceFloat() already has logic dealing with orthogonal
floats (bug 1141867), so this patch defers the decision to place a float below
the current line until the float's margin inline-size is computed in
FlowAndPlaceFloat().
Differential Revision: https://phabricator.services.mozilla.com/D151209
This patch is a preparation for the next part, and doesn't change the behavior
yet.
FlowAndPlaceFloat() is used to return true and false. This patch changes its
return value `true` to `PlaceFloatResult::Placed` and `false` to
`PlaceFloatResult::ShouldPlaceInNextContinuation`.
In the next part, we'll move the logic dealing with "below the current line
floats" into FlowAndPlaceFloat(), and make it return
`PlaceFloatResult::ShouldPlaceBelowCurrentLine`.
Differential Revision: https://phabricator.services.mozilla.com/D151208
First of all, `nsBlockFrame::AdjustFloatAvailableSpace()` is misleading. It
doesn't adjust the argument `aFloatAvailableSpace` at all, nor does it use any
fields in nsBlockFrame. It simply returns the available space in the parent
block's content area. Thus, I move it into BlockReflowState, and have it return
the available size rather than a rect because a size is sufficient for reflowing
a float.
Also, nsBlockFrame::ReflowFloat() only cares about the available size, but not
the position of the available space, so it is sufficient to pass a LogicalSize
computed by the new method ComputeAvailableSizeForFloat().
In FlowAndPlaceFloat(), there is a loop searching for a wide enough band to
place the float. We don't need to adjust availSize every time mBCoord is changed
in the loop. We can just call ComputeAvailableSizeForFloat() to get a new
available size before reflowing the float in the `!earlyFloatReflow` branch.
This patch shouldn't change the behavior.
Differential Revision: https://phabricator.services.mozilla.com/D151207
In FlowAndPlaceFloat(), condense two identical assertions about float frame
parent into one.
FlowAndPlaceFloat() calls ReflowFloat() only once, either an early reflow (when
`earlyFloatReflow` is `true`) or a late reflow (when `earlyFloatReflow` is
`false`), so the reflow status is always fresh.
Differential Revision: https://phabricator.services.mozilla.com/D151203
We have to make sure the scroll animations is still responsive at
boundaries even if it's playstate is finished.
This patch includes the update of UpdateFinishedState() to match the
spec, and make sure we still tick scroll animations at finished play state.
Getting a finished state might be strange for scroll animations, and this
might be a spec issue. However, for consistency with JS-generated animations,
we'd like to align the behaviors with other browsers, and make sure we are
still match the definition of finished state in the spec.
Besides, we have to use EndTime() on the compositor so
animation-iteration-count works properly.
Tests are in the last patch.
Differential Revision: https://phabricator.services.mozilla.com/D149940
Csoregi Natalia
Daisuke Akatsuka
David Shin
Kris Maglione
Iain Ireland
Mark Banner
Iulian Moraru
Mike Hommey
Morgan Reschenberg
Andrew Osmond
Emilio Cobos Álvarez
Markus Stange
Kagami Sascha Rosylight
Mozilla Releng Treescript
Ting-Yu Lin
Luca Greco
Neil Deakin
Tom Ritter
Boris Chiou
Meg Viar
Harveer Singh
Jan de Mooij