[pull] master from web-platform-tests:master #1893
Merged
+514
−151
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…override precedence. (#57427) * [wptrunner] Refactor preference building and fix override precedence. Restructure preference handling to build all preferences before profile creation, ensuring extra_prefs are applied last with proper type casting for correct override behavior. Split logic into _get_required_prefs(), and _get_default_prefs() for better code organization and maintainability. Differential Revision: https://phabricator.services.mozilla.com/D280722 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2012740 gecko-commit: e51fa869fc5ce33ff5075a9517b990d09368d965 gecko-reviewers: jgraham * Fix formatting of geo.provider.network.url preference * Fix formatting of geo.provider.network.url preference * Fix geolocation URL in Firefox Android preferences * Update geolocation URL in Firefox preferences --------- Co-authored-by: Henrik Skupin <mail@hskupin.info>
…test testing this behaviour Signed-off-by: rayguo17 <tin.tun.aung1@huawei.com>
Signed-off-by: rayguo17 <rayguo17@gmail.com>
This CL modifies the ellipsis functionality to handle cases where the ellipsis string value is bidirectional text. The `EllipsisShapeResult` class has been introduced since bidi runs require multiple ShapeResult objects along with their corresponding text and bidi levels. Additionally, the `ellipsis_shape_results_` has been changed to a vector to store these objects. Bug: 41492459, 479257822 Change-Id: I2ad35a55e780b7842936fee5f811edab213eecf2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6817921 Reviewed-by: Andreu Botella <abotella@igalia.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Minseong Kim <jja08111@gmail.com> Cr-Commit-Position: refs/heads/main@{#1577949}
Now it passes in all browsers. It was asserting on the wrong document after being adopted. Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
Differential Revision: https://phabricator.services.mozilla.com/D281143 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2010713 gecko-commit: 5c04e617c717f7542f27f1f4fc924325ef377e8e gecko-reviewers: firefox-svg-reviewers, longsonr
…ng failures at ignore-vertical-align.svg. DONTBUILD This reverts commit 3c61fdec1870dc64a28e3271b417b18be36bcdec. gecko-commit: dc1121d338857cc879d5a196a52a8a2edefcb158 gecko-reviewers: firefox-svg-reviewers, longsonr
Differential Revision: https://phabricator.services.mozilla.com/D281143 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2010713 gecko-commit: 4b27aa48d99259964dcb24246ef4d2850376347c gecko-reviewers: firefox-svg-reviewers, longsonr
Differential Revision: https://phabricator.services.mozilla.com/D281285 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2013429 gecko-commit: 102025d1bcfca4f5b92c97e11fb614d0254a42bc gecko-reviewers: layout-reviewers, TYLin
This CL modifies WebNN ORT backend to avoid resource exhaustion when multiple graphs are being compiled concurrently. It introduces a task runner dedicated to graph compilation tasks and queues all graph compilation tasks. It also introduces a cancelable task tracker to track and cancel graph compilation tasks if the context has been destroyed, preventing unnecessary resource consumption. Based on the restriction, the thread priority for background ORT session creation can be changed from `BEST_EFFORT`[1] to `USER_VISIBLE`, since `BEST_EFFORT` causes a compilation-time regression. The session creation tasks will be scheduled on foreground works with `USER_VISIBLE`. [1] https://chromium-review.googlesource.com/c/chromium/src/+/7318517 Bug: 474204746 Change-Id: I8208757221d2ab5dbd93603960c7c7e3a786f009 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7492170 Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com> Reviewed-by: Hu, Ningxin <ningxin.hu@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Xu, Mingming1 <mingming1.xu@intel.com> Cr-Commit-Position: refs/heads/main@{#1577997}
Set a page size that's large enough to hold the image. Images are monolithic. The ref uses a regular block, which is not monolithic. It probably passed in Firefox because firefox doesn't insert a break before the image, whereas Blink currently does. That seems rather irrelevant for this test, though. See https://crbug.com/40277379 Bug: 40886053 Change-Id: If0a0ed936f70d74de63e0d2ee5cfd5286e95ff19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7535253 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1577998}
This patch removes the `from-element` keyword from the CSS parser, as per the resolution[1] to change the CSS property for the responsive iframes. All changes are under an experimental runtime flag. [1] w3c/csswg-drafts#1771 (comment) Bug: 418397278 Change-Id: Ic22610419ce9029a81ca4b97ba15dc14d64107fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7534797 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Auto-Submit: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1578017}
We should only synthesize bold or oblique faces when font doesn't have any bolt or oblique faces correspondingly. However if variable font does support 'wght' or 'slnt' variable range but it's not reaching the threshold (600 for width or -14 for slant), we should not synthesize them on top. For instance if supported by the font 'slnt' range is ['-10', '0'] and user specified 'font-style: 20deg', we should not synthesize italic and use the maximum available slant, which is 10deg. Fixed: 40876291 Change-Id: Ie515d077bdeb337db3807de89e0f682cb455f7e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7532119 Commit-Queue: Munira Tursunova <moonira@google.com> Reviewed-by: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#1578044}
We weren't removing stylesheets when we should be doing so. This most notably happens when the stylesheet no longer has a href or its "rel" changes. The crash is also fixed, since the issue was that we were passing the value of the attribute that was changed as if it were an href. However, if we set the type attribute, then that's not the href. To fix that, we now retrieve the href inside the method so we always have the correct value. Fixes #42259 Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
10 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )