Comparing changes
Open a pull request
base repository: sailfishos-mirror/gecko-dev
base: 20e551c8eddb68a10ec88e7b5e252e1084767226
head repository: sailfishos-mirror/gecko-dev
compare: 347bc5719ad83cda5f8e53017cb2699b6004c27e
- 19 commits
- 181 files changed
- 13 contributors
Commits on Jun 29, 2021
-
Bug 1718196 - Revert back to 2px 3px padding-block on native XUL butt…
…ons, and add padding-inline of 5px r=emilio Differential Revision: https://phabricator.services.mozilla.com/D118923
-
Bug 1717185 - Fix mBufferedAmount and return value of send in TCPSock…
…et. r=valentin Previously, mBufferedAmount is only updated when copy complete. If I keep calling `send`, `NotifyCopyComplete` is only called after the last `send`. This patch changes to update mBufferedAmount in every `send` call, so that it returns `false` correctly if buffer is full. Differential Revision: https://phabricator.services.mozilla.com/D118258
Commits on Jun 30, 2021
-
Backed out changeset 875cd4a49df6 (bug 1717185) for failures on test_…
…tcpsocket_client_and_server_basics.html. CLOSED TREE
-
Bug 1718269 Renamed event that opens screenshots UI from the extensio…
…n.r=emalysz Differential Revision: https://phabricator.services.mozilla.com/D118855
-
Backed out changeset 7632b6b6aedc (bug 1717486) for causing build bus…
…tages on packager.mk. CLOSED TREE
Iulian Moraru committedJun 30, 2021 -
Bug 1718614 [wpt PR 29527] - Support 'only' keyword for color-scheme,…
… a=testonly Automatic update from web-platform-tests Support 'only' keyword for color-scheme Implements support for the keyword behind a flag, but does not have any effects on forced darkening yet. Bug: 1224806 Change-Id: I9b64ad706c7dd8fe68d3cf8838745e8e649a47ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2988314 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#896858} -- wpt-commits: e87ab351088662d35b41e27d2e8e8636beafc01d wpt-pr: 29527
-
Bug 1718614 [wpt PR 29527] - Update wpt metadata, a=testonly
wpt-pr: 29527 wpt-type: metadata
-
Bug 1718030 [wpt PR 29476] - Add WPT for COEP inheritance in local sc…
…heme workers, a=testonly Automatic update from web-platform-tests Add WPT for COEP inheritance in local scheme workers This change adds a Web Platform Test checking inheritance of Cross Origin Embedder Policy to dedicated/shared workers with blob or data URL. Change-Id: If307db134c6cfbcf8b8c768c57f3c6fbbee74b78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2984381 Reviewed-by: Domenic Denicola <domenic@chromium.org> Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Cr-Commit-Position: refs/heads/master@{#896862} -- wpt-commits: f28520b3049c78be94f73ff84e165d18dbc7ff83 wpt-pr: 29476
-
Bug 1718030 [wpt PR 29476] - Update wpt metadata, a=testonly
wpt-pr: 29476 wpt-type: metadata
-
Bug 1716975 [wpt PR 29411] - Test density size correction for cross-o…
…rigin images, a=testonly Automatic update from web-platform-tests Test density size correction for cross-origin images See whatwg/html#5574 -- wpt-commits: 2c19d6ee62676ac90146e7311ba13d8eaeb241fd wpt-pr: 29411
-
Bug 1716975 [wpt PR 29411] - Update wpt metadata, a=testonly
wpt-pr: 29411 wpt-type: metadata
-
Bug 1716846 [wpt PR 29402] - Add base plumbing for sync access handle…
…, a=testonly Automatic update from web-platform-tests Add base plumbing for sync access handle This CL adds createSyncAccessHandle() to FileSystemFileHandle, and its associated scaffolding. When creating a SyncAccessHandle, an OS-level file descriptor is returned by the browser. This is a temporary state to enable prototyping. When the file locking implementation becomes clearer, the browser will return a host object. Access to this surface is gated behind the --enable-features=FileSystemAccessAccessHandle content flag. For more context on this surface and the general objective of the merger between Storage Foundation and OPFS, check out: https://docs.google.com/document/d/1g7ZCqZ5NdiU7oqyCpsc2iZ7rRAY1ZXO-9VoG4LfP7fM Note: WPT tests are not marked as tentative because of crbug.com/1224358, they will be renamed after the bug is fixed. Bug: 1218431 Change-Id: I118a00cc6ea1bf2d1643d38f7716d001baa2b5ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2949473 Commit-Queue: Emanuel Krivoy <krivoy@google.com> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#896950} -- wpt-commits: dfeb97d188a94892304e7409dca3f814941821b9 wpt-pr: 29402
-
Bug 1716846 [wpt PR 29402] - Update wpt metadata, a=testonly
wpt-pr: 29402 wpt-type: metadata
-
Bug 1718606 [wpt PR 29525] - [Private Network Access] Add more web pl…
…atform tests., a=testonly Automatic update from web-platform-tests [Private Network Access] Add more web platform tests. This implements WPT RFC 72 support for the Blink web test runner. This draws on similar work done for wptrunner in the following WPT PR: web-platform-tests/wpt#28870 That PR taught wptserve how to run servers for http(s)-{private,public} ports and configure Chrome to treat those ports as belonging to the `private` and `public` address spaces. This CL teaches the Blink web test runner to do the same, then adds some tests verifying that. Bug: chromium:1138904 Change-Id: I7c118b64d62ac6932988ad40e370b0d7c72b56b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2987794 Commit-Queue: Titouan Rigoudy <titouan@chromium.org> Auto-Submit: Titouan Rigoudy <titouan@chromium.org> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Arthur Hemery <ahemery@chromium.org> Cr-Commit-Position: refs/heads/master@{#896984} -- wpt-commits: 9d1472176bfb1976157fb9891e2e1a34011f47d3 wpt-pr: 29525
-
Bug 1718606 [wpt PR 29525] - Update wpt metadata, a=testonly
wpt-pr: 29525 wpt-type: metadata
-
Bug 1718648 [wpt PR 29529] - Failure to repair missing parent when ar…
…ia-owns target destroyed, a=testonly Automatic update from web-platform-tests Failure to repair missing parent when aria-owns target destroyed Sometimes an AXObject doesn't need to be created for a DOM node because it doesn't participate in LayoutTreeBuilderTreversal. However, if aria-owns points to it, it will popup into existence as the child of another parent. If aria-owns is then cleared, AXRelationCache::UnmapOwnedChildren() will try to repair it back to the natural parent it had, but it never was able to have a natural parent in the first place, and rather than repairing the parent, the object should be removed from the AX tree. Bug: 1224119 Change-Id: I8cd415b9cd8ba766e71cc1007aec04bbcbfa6165 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2991297 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#897034} -- wpt-commits: d9b13e8b1a961c028f96758a810dbf633ea0b261 wpt-pr: 29529
-
Bug 1718689 - [wpt-sync] Update web-platform-tests to d9b13e8b1a961c0…
…28f96758a810dbf633ea0b261, a=testonly MANUAL PUSH: wpt sync bot wpt-head: d9b13e8b1a961c028f96758a810dbf633ea0b261 wpt-type: landing
-
Bug 1714914 - Make editor classes treat offset in parent node as uint…
…32_t r=m_kato It should be treated as `uint32_t` since DOM API does so. However, there are some exceptions: * Result of `nsINode::ComputeIndexOf()` * Result of `nsAString` methods They return `-1` as not found, and anyway, they cannot treat large integer than `INT32_MAX`. Therefore, this patch does not touch around them. Differential Revision: https://phabricator.services.mozilla.com/D118933
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 20e551c8eddb68a10ec88e7b5e252e1084767226...347bc5719ad83cda5f8e53017cb2699b6004c27e