Commit Graph

813937 Commits

Author SHA1 Message Date
Masayuki Nakano
4854c49121 Bug 1782911 - part 7: Make HTMLEditor::MoveOneHardLineContentsWithTransaction stop moving empty inline nodes r=m_kato
Empty inline nodes except non-container nodes are not required in the
destination paragraph.  Therefore, it should just remove the node from the
DOM tree.

Differential Revision: https://phabricator.services.mozilla.com/D157416
2022-09-25 12:49:45 +00:00
Masayuki Nakano
94fbe6ab47 Bug 1782911 - part 6: Make HTMLEditor::MoveOneHardLineContentsWithTransaction delete new empty inline parents if deleting unnecessary line break creates them r=m_kato
Differential Revision: https://phabricator.services.mozilla.com/D157415
2022-09-25 12:49:45 +00:00
Masayuki Nakano
a7c1b47e8b Bug 1782911 - part 5: Make HTMLEditor::AutoBlockElementsJoiner scan previous (or next) paragraph with ignoring invisible data nodes r=m_kato
We don't ignore invisible data node at joining 2 paragraphs and this is
a different behavior from the other browsers.  When looking for a content
from current block boundary, `AutoBlockElementsJoiner` should keep scanning
visible things with ignoring invisible data nodes.  Then, it should delete
all invisible things after joining the paragraphs.

Differential Revision: https://phabricator.services.mozilla.com/D157414
2022-09-25 12:49:44 +00:00
Masayuki Nakano
7e788541b1 Bug 1782911 - part 4: Make HTMLEditor::MoveNodeOrChildrenWithTransaction preserve white-space style at moving different style node r=m_kato
Chrome and Safari preserve `white-space` with `style` attribute to keep
collapsible or preserved white-spaces as-is.  If an HTML element is moved,
`style` attribute should be set to it.  Otherwise, create `<span>` element
whose `style` attribute has the declaration for `white-space` and move
content into it.

Differential Revision: https://phabricator.services.mozilla.com/D157413
2022-09-25 12:49:44 +00:00
Masayuki Nakano
bb2a35d9d7 Bug 1782911 - part 3: Make HTMLEditor always move first line of right block only when the blocks have different white-space style r=m_kato
Gecko just joins 2 blocks when editable block parents are same element, e.g.,
both are `<div>`.  However, Chrome and Safari moves only first line of the
right block into the left block, and Gecko does it when both blocks are
different elements.

Ideally, we should take same behavior as Chrome and Safari because it's
reasonable for both compatibility with the other browsers and consistency
when both blocks are different but has same style, then we don't need to
maintain different behavior paths.

However, doing it for all elements are too risky because right block will be
merged into left block if right block has no line break.  On the other hand,
without doing it, preserving `white-space` is really hard because we need to
maintain the both paths.

Therefore, I'd like to change the behavior only when both blocks have different
`white-space` styles.  Usually, web apps do not change `white-space` for each
block, so I think that this is safer than doing this in all elements,
additionally, we can revert the behavior easy since this patch is really small.

Differential Revision: https://phabricator.services.mozilla.com/D157412
2022-09-25 12:49:43 +00:00
Masayuki Nakano
d1b5e4a973 Bug 1782911 - part 2: Clean up unnecessary line break at block boundary while moving first line of right paragraph to left paragraph r=m_kato
This fixes bug 503838 partially.  The new utility method scans unnecessary
`<br>` with strict check as far as possible.  Then, we can delete the node or
the preformatted line break at end of the last text node.

Differential Revision: https://phabricator.services.mozilla.com/D157411
2022-09-25 12:49:43 +00:00
Masayuki Nakano
222a330cb6 Bug 1782911 - part 1: Port most tests of test_bug772796.html to WPT r=m_kato
This patch ports most part of `editor/libeditor/tests/test_bug772796.html` to
WPT because this kind of behaviors are not tested by `editing/run/delete.html`
nor `editing/run/forwarddelete.html`. (Not ported tests are invalid HTML
structure cases and list item cases, the reason why not doing this for the
latter is, it needs a lot of cases and not important for most web apps.)

The most expectations are based on Chrome and Safari (they both behave almost
same), but they fail a lot in `join-pre-and-other-block.html` and
`white-space: pre-line` cases in the other tests.

Even though this ports a lot of cases, for making easier to compare the
behavior change in the following patches, we should keep the tests.

Differential Revision: https://phabricator.services.mozilla.com/D157410
2022-09-25 12:49:42 +00:00
Ted Campbell
7a57865285 Bug 1790912 - Migrate js/ductwork/debugger to devtools/platform. r=ochameau
This gecko integration code is better managed with the other devtools platform
hook code. To simplify resolving the JSM and avoiding issues around restricted
use of eval in chrome, I also reset the DIST_SUBDIR config and run the xpcshell
tests without a firefox-appdir. The test works on Android these days, so
re-enable it on that platform.

Differential Revision: https://phabricator.services.mozilla.com/D157522
2022-09-25 09:03:34 +00:00
Ted Campbell
410e8dff3f Bug 1790912 - Fix lint issues in js/ductwork/debugger. r=ochameau
When we move this out of the js/ directory, a number of lint exceptions stop
applying so we should just fix the issues now.

Differential Revision: https://phabricator.services.mozilla.com/D157521
2022-09-25 09:03:33 +00:00
Ted Campbell
69dfb519c2 Bug 1790912 - Use globalThis instead of this with jsdebugger.jsm. r=jandem,ochameau
Use 'globalThis' instead of 'this' when trying to attach a debugger to the
current global to avoid subtle footguns with the varied definitions of 'this'.
The debugger interface needs a true GlobalObject so this is much clearer. In
particular, this is a problem in test_nativewrappers.js when the test runs in
strict mode since the 'this' in the test function is no long implicitly the
global.

Differential Revision: https://phabricator.services.mozilla.com/D157544
2022-09-25 09:03:33 +00:00
Mozilla Releng Treescript
70902f1067 no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD CLOSED TREE
sl -> ad95573f93ba628d14ded08ed14dc585ba0ca8dd
sv-SE -> 13c7bce8d37954d32cb6a736e944eb65fb4957bf
tg -> 0856230c9cbd021338626886d7bb4629d8bbef77
2022-09-25 06:59:06 +00:00
Dan Robertson
607672e1b4 Bug 1655598 - Cross origin image request should not respect image orientation. r=emilio
A cross origin image request should not respect the given style image
orientation, but should use any image orientation provided by the image.

Differential Revision: https://phabricator.services.mozilla.com/D156919
2022-09-25 00:07:56 +00:00
Dan Robertson
6b7a505d18 Bug 1655598 - The imgIRequest uri attribute should be infallible. r=emilio
The implementation of GetURI always returns NS_OK, and therefore the URI can
be marked as infallible.

Differential Revision: https://phabricator.services.mozilla.com/D157009
2022-09-25 00:07:55 +00:00
Andrew McCreight
098ef6e21d Bug 1543537, part 3 - Cycle collect subject-to-finalization nsXPCWrappedJS. r=kmag
nsXPCWrappedJS use a special extra refcount to support weak references. When
a WJS is held alive only by this refcount, instead of holding its JS object
alive, the JS object holds it alive. This patch adds support for properly
cycle collecting WJS in this state. First, it makes it so the CC will traverse
these WJS, so that it has a chance to collect them. Secondly, it represents
the reference from the JS object to the WJS via the NoteWeakMapping API.
This lets us represent a strong reference outside of the actual object.

This also adds some basic tests for the lifetime of WJS with weak references.
The first two tests pass with and without this patch. This patch makes the
third test pass.

Differential Revision: https://phabricator.services.mozilla.com/D157672
2022-09-24 23:24:31 +00:00
Andrew McCreight
02175411d0 Bug 1543537, part 2 - Maintain and suspect a list of WJS that are subject to finalization. r=kmag
The cycle collector needs to be able to see nsXPCWrappedJS that are held
alive only from JS in order to unlink them. This patch adds a linked
list of WJS that are subject to finalization, and suspects those WJS in
the CC. Wrapped JS are normally suspected via the JS holder mechanism,
but that skips things, like WJS subject to finalization, that aren't holding
alive JS objects.

Differential Revision: https://phabricator.services.mozilla.com/D157671
2022-09-24 23:24:31 +00:00
Andrew McCreight
b6da7dc336 Bug 1543537, part 1 - Add a NoteWeakMapping method to traversal callback. r=kmag
For nsXPCWrappedJS, we need to add an edge to the cycle collector graph
from the JS object to its WJS, even though the JS object does not actually
contain a pointer to the WJS object. We can (mis)use the weak mapping
interface for this purpose. The only difference is that we need it during
traversal instead of while adding roots. The API is fairly specialized to
the specific use case we need.

Differential Revision: https://phabricator.services.mozilla.com/D157529
2022-09-24 23:24:31 +00:00
Butkovits Atila
5dd1f5147d Backed out changeset f6031e0a3a0b (bug 1790790) for causing telemetry failures. CLOSED TREE 2022-09-25 02:06:13 +03:00
Dale Harvey
7c34f3100d Bug 1790790 - Add Nimbus flag to control Search Private Default. r=Standard8
Differential Revision: https://phabricator.services.mozilla.com/D157605
2022-09-24 21:12:51 +00:00
Mozilla Releng Treescript
fbd9515669 no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD CLOSED TREE
el -> c59accc26966bf0407aa52dae13849f690a4e660
hsb -> 00aa7accc4afa6b3d673549672e8ae8ca4cea036
lo -> 9df93aa052ab6767b6de7646904e300487a32dad
pt-BR -> 4f3ffff1dc1a8b646c7eb0e9808ca9b3ce24cf2b
ru -> 24d7fc43db0657a61154aa83c7e68705a25ca962
te -> 1dbcaec6b941b0f4de9570fada823ffd92858ebf
tg -> 94d2add01606b64df29ebea9a70e06f51b291c6d
tr -> 998d601f5e6bb1a5d402854c086405ff2a3ea898
uk -> 668c5c16ada5d9d8a2e41b5f288e12528f132d9d
vi -> 1f0eace8a51726d411233378ec2bf7d26d5483ab
2022-09-24 19:06:29 +00:00
Gabriele Svelto
08f27c6049 Bug 1790079 - NULL-check the values returned by RandR queries before using them r=jgilbert
Differential Revision: https://phabricator.services.mozilla.com/D158005
2022-09-24 09:23:07 +00:00
Alexandre Poirot
5bae281ff6 Bug 1791055 - [devtools] Migrate to CommandsFactory to instantiate all descriptors. r=jdescottes,perftest-reviewers,AlexandruIonescu
This help factorise all code trying to instantiate a server and a client everywhere.
This will also help migrate from descriptor to commands in Toolbox constructor.

A good way to track all leftover manual instantiation of descriptors is to look for mainRoot.get*.
There should only be tests now, and descriptor-from-url, which I would to convert once
we migrate toolbox constructor from descriptor to commands.

Differential Revision: https://phabricator.services.mozilla.com/D157737
2022-09-24 07:14:58 +00:00
Mozilla Releng Treescript
bed23da9dc no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD CLOSED TREE
en-GB -> 787c5411bcccf296f8c722235b77b461ec42344a
es-AR -> 4d99d13ef695260c46d5a3eaa321840062bdbd71
es-CL -> 10f435e12d441a2baa051cff443d9f08ca253c04
si -> e6b1dbdfc7beb4d7745c4753e8eddcdff45ea6d5
sl -> 9a59b15a94f93aecbc6645cd67c407974f69cd76
tg -> db7d7b04b90ab8c45a64fb08e3c7481a74133808
uz -> 9585a66b83d39237ebc2627a363c79869546522e
2022-09-24 06:57:57 +00:00
Shane Hughes
cdbf03e2df Bug 1789644 - Add a pref toggle for QuickActions, separate from the pref for suggestions. r=mak,daleharvey
Change the behavior of the QuickActions provider, so that setting the
pref `quickactions.enabled` to false will prevent showing quick action
results in all contexts, while setting `suggest.quickactions` to false
will only prevent showing quick action results in the default search
mode (i.e., quick action results will still appear in the Quick Actions
search mode enabled by typing `> ` in the urlbar).

Differential Revision: https://phabricator.services.mozilla.com/D157702
2022-09-24 00:00:46 +00:00
Emily McMinn
e13bcf2405 Bug 1790396 - Fixup Feature Callout button CSS for HCM r=aminomancer
Differential Revision: https://phabricator.services.mozilla.com/D158036
2022-09-23 23:59:14 +00:00
Sandor Molnar
864b7a93a2 Backed out 3 changesets (bug 1791682) for causing spider monkey failures. CLOSED TREE
Backed out changeset c7e6bf99e7f7 (bug 1791682)
Backed out changeset 5be243995b2f (bug 1791682)
Backed out changeset a2e1831539e7 (bug 1791682)
2022-09-24 02:53:46 +03:00
Oriol Brufau
70bc1e8b84 Bug 1792217 - Let last remembered size take all fragments into account regardless of pref. r=emilio
ResizeObserver only handles multiple fragments when the preference
dom.resize_observer.support_fragments is true.
That's because this experimental behavior may have compat problems.

But the last remembered size uses an internal ResizeObserver,
so changing the signature of the callback is not a problem.

Differential Revision: https://phabricator.services.mozilla.com/D158034
2022-09-23 23:41:34 +00:00
Ray Kraesig
f88d2cb267 Bug 1791682 - [3/3] Remove thread names only used in tests r=andi
Remove all the thread names only used in tests from ThreadAllows.txt.
Instead, list the test files that create them in ThreadFileAllows.txt.

Differential Revision: https://phabricator.services.mozilla.com/D157762
2022-09-23 23:11:14 +00:00
Ray Kraesig
c2e8c8663e Bug 1791682 - [2/3] Allow multiple path-elements in ThreadFileAllows.txt r=andi
Filenames alone do not uniquely identify files in the Mozilla codebase.
Allow specification of path-elements alongside filenames.

Differential Revision: https://phabricator.services.mozilla.com/D157761
2022-09-23 23:11:13 +00:00
Ray Kraesig
06b7e76be7 Bug 1791682 - [1/3] Allow comments in thread-checker definition files r=andi
Expand the processor for ThreadAllows.txt and ThreadFileAllows.txt to
also recognize and permit comments prefixed by `#`.

Differential Revision: https://phabricator.services.mozilla.com/D157760
2022-09-23 23:11:13 +00:00
moz-wptsync-bot
c1e4185a4d Bug 1791857 - [wpt-sync] Update web-platform-tests to 0865ba27228c2560fdd8601d2cd53537554ad50b, a=testonly
MANUAL PUSH: wpt sync bot

wpt-head: 0865ba27228c2560fdd8601d2cd53537554ad50b
wpt-type: landing
2022-09-23 22:53:45 +00:00
moz-wptsync-bot
914c76a384 Bug 1791507 [wpt PR 35960] - Update wpt metadata, a=testonly
wpt-pr: 35960
wpt-type: metadata
2022-09-23 22:53:44 +00:00
Ming-Ying Chung
f3a1b3a959 Bug 1791507 [wpt PR 35960] - [beacon-api] Fix sendondiscard web tests's assertions, a=testonly
Automatic update from web-platform-tests
[beacon-api] Fix sendondiscard web tests's assertions

1. Move sendondiscard web tests to `wpt_internal/`:

   Tests in this file were not working properly as the BackgroundSync
   permission is set to `Denied` by default in the web test runner.
   Moving to `wpt_internal/` allows the use of
   `internals.setPermission()` API.

2. There was also a bug in `expectBeacon()` function which didn't
   check the total number of sent beacons properly.

This CL fixes the above issues.

Bug: 1293679,1364348
Change-Id: Ia037080f94303279154fa0d71d33cf364712590c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3907264
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Ming-Ying Chung <mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1049485}

--

wpt-commits: 5d424eb8c75dee2c8c11f4d5db17ee4e31fe1a71
wpt-pr: 35960
2022-09-23 22:53:43 +00:00
moz-wptsync-bot
a00f689073 Bug 1791703 [wpt PR 35988] - Update wpt metadata, a=testonly
wpt-pr: 35988
wpt-type: metadata
2022-09-23 22:53:42 +00:00
Miyoung Shin
7e5e0010f2 Bug 1791703 [wpt PR 35988] - Prerender: Upstream tests for cross-origin iframe in prerendered pages, a=testonly
Automatic update from web-platform-tests
Prerender: Upstream tests for cross-origin iframe in prerendered pages

This CL upstreams tests for the cross-origin iframe including
a sandbox iframe in prerendered pages to the WPT repository.
sandbox iframes should be treated as the cross-origin iframe
specified in the draft spec:
https://wicg.github.io/nav-speculation/prerendering.html#delay-crossorigin

Bug: 1253158
Change-Id: Id34264eaec7584fbef38844a20ef8c15636d156d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3908027
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1049479}

--

wpt-commits: dd968b9c3f154a515342d1f57b8c722ef6da4d6f
wpt-pr: 35988
2022-09-23 22:53:42 +00:00
Kent Tamura
8661e046b4 Bug 1791660 [wpt PR 35983] - FrameSet NG: Fix a crash on re-showing a sub FRAMESET, a=testonly
Automatic update from web-platform-tests
FrameSet NG: Fix a crash on re-showing a sub FRAMESET

We clear NeedsLayout flags of FRAMESET children which are not fit in
the FRAMESET's grid. We should clear their NGPhysicalFragments too in
order not to re-use stale fragment trees when a child fits in the grid
again.

Bug: 1365048
Change-Id: I638f68eba61d557b1aede9d4f686998f0c774d60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3904719
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1049471}

--

wpt-commits: b4cafb54ac6b0835c8b09174d2b92cb123b2afbd
wpt-pr: 35983
2022-09-23 22:53:41 +00:00
moz-wptsync-bot
99851d0d0a Bug 1791577 [wpt PR 35968] - Update wpt metadata, a=testonly
wpt-pr: 35968
wpt-type: metadata
2022-09-23 22:53:41 +00:00
Julie Jeongeun Kim
24a4859a4a Bug 1791577 [wpt PR 35968] - Prerender2 WPT: Externalize clients.matchAll() web platform test, a=testonly
Automatic update from web-platform-tests
Prerender2 WPT: Externalize clients.matchAll() web platform test

Bug: 1253158
Change-Id: I8c167b133f7abd62b0a73448cd56c222f75c18ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3906662
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1049451}

--

wpt-commits: 86a71db107da70c6284bd21c5d6bcff7b3685e27
wpt-pr: 35968
2022-09-23 22:53:40 +00:00
moz-wptsync-bot
629a982374 Bug 1791500 [wpt PR 35959] - Update wpt metadata, a=testonly
wpt-pr: 35959
wpt-type: metadata
2022-09-23 22:53:40 +00:00
Yeunjoo Choi
eb05d07840 Bug 1791500 [wpt PR 35959] - Prerender: Upstream tests for the referrer on prerendering navigation, a=testonly
Automatic update from web-platform-tests
Prerender: Upstream tests for the referrer on prerendering navigation

This CL upstreams tests that prerender uses the page's default referrer
policy. The behavior isn't described in spec, but discussed in [1].

[1] https://github.com/WICG/nav-speculation/issues/51

Bug: 1253158
Change-Id: I8ea931af24ecefc8da84f9710945b36c8e1ea98d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3907161
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Yeunjoo Choi <ychoi@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1049450}

--

wpt-commits: c607b88000b40a6d41005087c499f52eb5734dfd
wpt-pr: 35959
2022-09-23 22:53:39 +00:00
moz-wptsync-bot
12ebc3f3ae Bug 1791662 [wpt PR 35984] - Update wpt metadata, a=testonly
wpt-pr: 35984
wpt-type: metadata
2022-09-23 22:53:39 +00:00
L. David Baron
7fb203767d Bug 1791662 [wpt PR 35984] - Make multiple-centered-dialogs.html handle different zoom levels better., a=testonly
Automatic update from web-platform-tests
Make multiple-centered-dialogs.html handle different zoom levels better.

This changes the test to get the necessary heights with subpixel
precision rather than with getters that round to pixels, and then
expects the result to be accurate within 0.05px.  These sizes may be
subpixel values when the device-pixel-scale is not an integer.

Fixed: 1365295
Change-Id: I1107a60cb8ff39f8d028f54a37b5ba13ab7b678b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3906230
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1049441}

--

wpt-commits: 51085f9ff9bf6685b3bb5664cb9d6f1f82c27933
wpt-pr: 35984
2022-09-23 22:53:38 +00:00
dependabot[bot]
904ae4227d Bug 1791462 [wpt PR 35954] - Bump taskcluster from 44.18.0 to 44.21.0 in /tools, a=testonly
Automatic update from web-platform-tests
Bump taskcluster from 44.18.0 to 44.21.0 in /tools

Bumps [taskcluster](https://github.com/taskcluster/taskcluster) from 44.18.0 to 44.21.0.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taskcluster/taskcluster/compare/v44.18.0...v44.21.0)

---
updated-dependencies:
- dependency-name: taskcluster
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
--

wpt-commits: f96321cbef3294ee6244cbe1aa6d194c3b7103cc
wpt-pr: 35954
2022-09-23 22:53:38 +00:00
moz-wptsync-bot
ab735619d7 Bug 1791601 [wpt PR 35971] - Update wpt metadata, a=testonly
wpt-pr: 35971
wpt-type: metadata
2022-09-23 22:53:37 +00:00
Koji Ishii
44b95131a3 Bug 1791601 [wpt PR 35971] - [anchor-position] Support nested block fragmentation, a=testonly
Automatic update from web-platform-tests
[anchor-position] Support nested block fragmentation

In a nested block fragmentation context, fragmentainers of the
inner context may not have the correct block offsets. This is
intentionally omitted because it is expensive, and it is not
necessary for existing usages.

However, when anchors in the nested multicol is fragmented by
the outer multicol, anchor query needs the offsets. This patch
changes to let anchor query to search anchors from the outer
block fragmentation context in such cases.

|NGLogicalAnchorQueryForFragmentation| can find fragments and
their offsets by traversing descendants. By giving the outer
block fragmentation context to it, it can determine the
correct offsets of the inner fragmentainers.

Bug: 1309178
Change-Id: I0e98ed8b345b3fda1a08d9bb5b4e25cb7903f306
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3881852
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1049351}

--

wpt-commits: 42108c3d10b6982fc52fbdd678f8e1cfdf3f2bd4
wpt-pr: 35971
2022-09-23 22:53:37 +00:00
moz-wptsync-bot
cf5eeba1f5 Bug 1791654 [wpt PR 35982] - Update wpt metadata, a=testonly
wpt-pr: 35982
wpt-type: metadata
2022-09-23 22:53:36 +00:00
Ian Kilpatrick
464a3b7e4d Bug 1791654 [wpt PR 35982] - [last-baseline] Add tests for fieldsets., a=testonly
Automatic update from web-platform-tests
[last-baseline] Add tests for fieldsets.

As above.

Bug: 885175
Change-Id: Ic232a0dc2b0c4f2516cfb7e1dadd0c6d7315b866
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3908447
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1049344}

--

wpt-commits: 3b94cbbe6e52bfe0788f2b535604a66b054dea8f
wpt-pr: 35982
2022-09-23 22:53:36 +00:00
moz-wptsync-bot
bd3ec420d3 Bug 1791631 [wpt PR 35977] - Update wpt metadata, a=testonly
wpt-pr: 35977
wpt-type: metadata
2022-09-23 22:53:35 +00:00
Ian Kilpatrick
665ae0361c Bug 1791631 [wpt PR 35977] - [last-baseline] Fix alignment baseline for spanning items., a=testonly
Automatic update from web-platform-tests
[last-baseline] Fix alignment baseline for spanning items.

When introducing the minor baseline groups we didn't set/get the
baseline from the correct set.

This changes the logic such that when use access a minor baseline we
use the end set.

Bug: 885175
Change-Id: I88f1d8fce2fc056d971fc7c4cc4c75ec50d232a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3905711
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1049300}

--

wpt-commits: 3505e87ffb37558ea29d04778726a2c79ed8d61a
wpt-pr: 35977
2022-09-23 22:53:34 +00:00
moz-wptsync-bot
fd71cd00a8 Bug 1791612 [wpt PR 35976] - Update wpt metadata, a=testonly
wpt-pr: 35976
wpt-type: metadata
2022-09-23 22:53:34 +00:00
Ian Kilpatrick
13691f1be4 Bug 1791612 [wpt PR 35976] - [last-baseline] Propagate last-baseline from tables., a=testonly
Automatic update from web-platform-tests
[last-baseline] Propagate last-baseline from tables.

For more details see:
https://github.com/w3c/csswg-drafts/issues/7655#issuecomment-1248528627

Effectively we should propagate the last-baseline from the last
table-row (we ignore caption baselines for example).

If the row is baseline aligned (using vertical-align: baseline) this
becomes the first & last baseline (until we support
"align-content: last baseline"), otherwise we use the lowest
content-edge.

Bug: 885175
Change-Id: Id9de2f8baff5511fd4da2cef3f056c1bac0fc112
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3907838
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1049240}

--

wpt-commits: 55e1c625687971d6e9ad0836127bb2f679f33123
wpt-pr: 35976
2022-09-23 22:53:33 +00:00