Automatic update from web-platform-tests
MathML: Add tests for children not participating to their parent layout (#18293)
* MathML: Add tests for children not participating to their parent layout
This commit adds new tests to verify that children with "display: none",
"position: absolute" or "position: fixed" don't affect preferred width
calculation or layout of their parents.
- mathml/support/mathml-fragments.js: Add function to append a non empty
child (optionally making the element invalid) and use that function for
forceNonEmptyElement.
- mathml/support/layout-comparison.js: Introduce new helpers function to
extract the children participating to their parent layout. Modify
compareLayout so that it browser that list of children instead and allow
comparison in horizontal+LTR mode.
* Add feature detection otherwise these tests pass when MathML is disabled.
* Add TODO for floats.
--
wpt-commits: 7a669f450b8ffbc803a3206bee36733e06773e90
wpt-pr: 18293
Automatic update from web-platform-tests
Enable "RestrictedWebkitAppearance" flag as "experimental".
* insert_paragraph_separator_command_test.cc
<colgroup>'s actual appearance will be 'none', and it has no height.
* external/wpt/css/css-lists/list-and-margin-collapse-003.html and -004.html
<div> can't have 'checkbox' appearance any longer, and we couldn't find other
ways to reproduce the original issue. So we remove the tests.
* fast/css/invalid-appearance.html
Removed. It was made to check deprecation messages.
* fast/css/square-button-appearance.html
Removed. -webkit-appearance:square-button doesn't work for arbitrary elements
any longer, and its appearance is tested in input[type=color] tests.
* fast/forms/file/file-style-inheritance.html
-webkit-appearance:square-button doesn't work for ::-webkit-file-upload-button
any longer. -webkit-appearnace:none works well in the test.
* fast/forms/range/thumbslider-no-parent-slider.html
-webkit-appearance:slider-thumb-* don't work in this case any longer. Its
pixel result has nothing. This CL converts the test to a reference test.
* scrollbars/custom-scrollbar-appearance-property.html
-webkit-appearance:searchfield-cancel-button doesn't work for
::-webkit-scrollbar* any longer, and pixel result of this test would be
changed. This CL converts the test to a testharness.js test.
* fast/css/invalid-appearance-progress-bar-meter-expected.txt
* fast/forms/datalist/slider-appearance-with-ticks-crash-expected.txt
* fast/forms/range/slider-appearance-crash-expected.txt
* fast/forms/range/thumbslider-crash-expected.txt
* fast/text/whitespace/pre-block-normal-inline-crash-2-expected.txt
* paint/invalidation/selection/multiple-body-remove-selection-crash-expected.txt
* paint/theme/anonymous-element-menulist-painting-expected.txt
Remove deprecation messages.
Bug: 981720
Change-Id: I91068c8265cdfc682a06b1b4588b04ea30a318d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727654
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#684247}
--
wpt-commits: 10137469748fa74d86e02243c6aae6e45e76e1f0
wpt-pr: 18277
Automatic update from web-platform-tests
Replaced elements with 'contain: size' should have zero intrinsic size.
This behavior follows the spec,
https://drafts.csswg.org/css-contain/#containment-size,
as the statement below.
'Replaced elements must be treated
as having an intrinsic width and height of 0.'
For this behavior, when 'contain: size' is specified,
LayoutReplaced::IntrinsicSize returns zero size
instead of the intrinsic size it actually has.
Before this CL,
|LayoutReplaced::ComputeIntrinsicSizingInfoForReplacedContent|
did early return with "FloatSize()",
but |LayoutReplaced::ComputeReplacedLogicalWidth| has *if statement*
for specified and intrinsic css size,
so *that* early return couldn't be reached.
Addition to it, ComputeIntrinsicSizeFoo uses
|LayoutReplaced::IntrinsicSize| essentially,
and it returned non-zero size and that value was used before this CL.
Bug: 955163
Change-Id: If0309ae5f1adb2e3026ff92bfde2ffb07ba73582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1703540
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Joonghun Park <pjh0718@gmail.com>
Cr-Commit-Position: refs/heads/master@{#684192}
--
wpt-commits: 2cc953df18d460ae7cdac64359660a9de3e90019
wpt-pr: 17876
Automatic update from web-platform-tests
Update current_frame
When a setTargetAtTime event has converged (10 time constants), we
basically hold the value. However, if there's a setValue event after
convergence, and this setValue is within the current render quantum,
the current_frame was not getting updated, so when this event and the
next are getting processed, the currentTime has the incorrect value.
Update current_frame appropriately in this case.
Bug: 990393
Test: the-audioparam-interface/set-target-conv.html
Change-Id: I4b364d3972e1f5acb454916fdb6455fb75b7e7b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1736173
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#684137}
--
wpt-commits: ea702882ef9071620da2d32dc2542f3b7b2e6116
wpt-pr: 18282
Automatic update from web-platform-tests
[css-flexbox] Test for definite flex basis of fully inflexible item
Safari and blink legacy fail this; EdgeHTML, Firefox, and blink NG pass
it, but I think blink NG passes it by accident for now.
Change-Id: I38acc8ba98d3897aa77305a36c2ae6f2affec640
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713143
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#684111}
--
wpt-commits: 78490291ac0bd985de553d2c5f33d13ddaf4651e
wpt-pr: 18025
Automatic update from web-platform-tests
Translate 25 more svg/animation tests to WPT
This is the second commit in the series of updating all the old svg
animation tests.
The usage of testharness has replaced the older SVGAnimationTest.js
for all where it's suitable. No functionality should have changed
and the tests should cover almost the same.
In all of the animations where there is a sampling at T=0, where
it was assumed that no animations had started. Which didn't work
flawlessly when moved to the new system, it has thus been removed.
Bug: 985335
Change-Id: If5d6d879be3ccd3b14467eebaa4c9a2c03128f64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733589
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683944}
--
wpt-commits: dcdebb1b8e7d3f9a4650498c1efeae78060294e5
wpt-pr: 18257
Automatic update from web-platform-tests
MathML: Make box comparison more reliable by using an absolutely-positioned div. (#18276)
It seems padding/border/margin-002 tests may fail because of interaction between
sibling divs. Although this probably need separate debugging/testing, these
tests are intended to verify each subtest individually, so make the testing divs
absolutely-positioned in order to isolate them from the rest of the layout.
--
wpt-commits: d250e8cd5fe0cb3c80cb0fdfc2040f4cfcbf7a0d
wpt-pr: 18276
Automatic update from web-platform-tests
Translate 25 tests to WPT
This is the second commit in the series of updating all the old svg
animation tests.
The usage of testharness has replaced the older SVGAnimationTest.js
for all where it's suitable. No functionality should have changed
and the tests should cover almost the same.
In all of the animations where there is a sampling at T=0, where
it was assumed that no animations had started. Which didn't work
flawlessly when moved to the new system.
Bug: 985335
Change-Id: I789c1a020ee9004f4cfb7fe4292ba80f318aeeee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730904
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683926}
--
wpt-commits: c83df3d495977e1faca01565ddde69053f19ba71
wpt-pr: 18235
Automatic update from web-platform-tests
[LayoutNG] Fix PDI/PDF not to affect line breaking
This patch fixes PDI/PDF before spaces not to suppress the
line breaking opportunity at the space. For example, before
this fix, `<bdo dir=ltr>a</bdo> b` could not break between
"a" and "b".
PDI and PDF are injected by the `unicode-bidi` property, or
elements that imply the `unicode-bidi` property such as
`<bdi>`, `<bdo>`, or any elements with `dir` attributes.
Bug: 989094
Change-Id: I2128774e2b062ecb86880812c54d46299a19a18a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1735146
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683881}
--
wpt-commits: 32fc57874bfa01d7526f6a434c5ccb67b16337cd
wpt-pr: 18275
Automatic update from web-platform-tests
Add tentative idl tests (#18237)
Add tests for all developer visible effects of suggested changes to add IDL which normalizes MathML elements with the rest of the platform:
* Add global events support test
* add tentative tests for HTMLOrForeignElement
* Add tentative tests for ElementCSSInlineStyle interfaces
* Add tentative tests DocumentAndElementEventHandlers
Note: There are no IDL tests itself as how this is achieved is secondary to the actual goals of making MathML elements 'normal'.
--
wpt-commits: 533a5dc6ff20099a1ef18b0724add2b59fbcb2f1
wpt-pr: 18237
Off-thread tasks now use a pool of JSContexts (for compatibility with the XPCOM thread pool).
Tasks that don't need a JSContext can run without one (nullptr TlsContext). We can now do this
for Ion and Wasm tasks too.
Depends on D41380
Differential Revision: https://phabricator.services.mozilla.com/D41381
--HG--
extra : moz-landing-system : lando
Some functions that are called from the Ion backend use AutoUnsafeCallWithABI.
Initially I wanted to fix this by splitting these functions in two separate
functions, but this doesn't work well for all the Math builtins that are called
by GVN.
Depends on D41379
Differential Revision: https://phabricator.services.mozilla.com/D41380
--HG--
extra : moz-landing-system : lando
This will allow us to run off-thread Ion tasks without a JSContext.
I renamed IonCompiling and IonCompilation to IonBackend to make it
clearer that this doesn't include IonBuilder time.
Differential Revision: https://phabricator.services.mozilla.com/D41379
--HG--
extra : moz-landing-system : lando
This patch changes how a VarCache pref works when deleted (in some cases) --
the VarCache variable keeps its existing value instead of being reset to a
pre-specified default.
In bug 1570212 I have made sure that no VarCache prefs exhibit this behaviour
in practice any more, so this change should not affect functionality. There is
an assertion that checks this.
The next patch will take advantage of this change by removing the need to
store the pre-specified defaults, which will save memory.
Differential Revision: https://phabricator.services.mozilla.com/D39805
--HG--
extra : moz-landing-system : lando
If the login is older than 2 minutes, don't allow revealing the password in the doorhanger.
Differential Revision: https://phabricator.services.mozilla.com/D40434
--HG--
extra : moz-landing-system : lando
Investigation showed that on this platform the texture unit state becomes
corrupted whenever we set the non-identity swizzling (getting garbage from textureSize()).
Given no easy workaround, we disable swizzling for this GPU family on Mac, for now.
Differential Revision: https://phabricator.services.mozilla.com/D41274
--HG--
extra : moz-landing-system : lando
