Refactor the error message with the adding the information from the imported
module, for example:
// a.mjs
import { a } from "./b.mjs";
// b.mjs
const b = 1;
Originally the error message is "import not found: default", now it
becomes "The requested module: b.mjs doesn't provide an export named: a"
// c.mjs
import { c } from "./d.mjs";
// d.mjs
export * from "./d1.mjs";
export * from "./d2.mjs";
// d1.mjs
export const c = 1;
// d2.mjs
export const c = 2;
Originally the error message is "ambiguous import: c", now it becomes
"The requested module d.mjs contains ambiguous star export: c from
d1.mjs and d2.mjs"
Add another error message for circular import:
// e.mjs
export { e } from "f.mjs";
// f.mjs
export { e } from "e.mjs";
Originally it was "indirect export not found: e", now it is
"The request module: f.mjs contains circular import: e".
Differential Revision: https://phabricator.services.mozilla.com/D200345
Changes:
- implement exnref type and try_table opcode.
- fix text representation of some ref and relaxed_simd ops
Tests are provided in the upstream repository.
Differential Revision: https://phabricator.services.mozilla.com/D204785
In case we did start a DeleteFilesRunnable before shutdown we should ensure it is going to be executed before we leave our QM shutdown barrier, but we can ignore pending but not yet started deletions completely as PBM origins are deleted entirely by other means.
Differential Revision: https://phabricator.services.mozilla.com/D203502
I think we should start off with this. Other platforms can implement
this too, but exposing this to content seems like quite the rabbit hole.
Differential Revision: https://phabricator.services.mozilla.com/D203405
Version 0.32 of audio_thread_priority no longer links statically with
avrt.dll, which should help with the crash from bug 1884214.
Differential Revision: https://phabricator.services.mozilla.com/D204747
Automatic update from web-platform-tests
[css-anchor-position] Remove support for position-fallback property
position-fallback is no longer in the spec, has no effect in application
of position fallback, and position-try-options has replaced it.
Bug: 40279608
Change-Id: I21f6a3e51623e0580608ccf0891b42d73dcbfd3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5371763
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1273323}
--
wpt-commits: 561ebc0f1ed10cdce8067952ac638ad86953a255
wpt-pr: 45104
Automatic update from web-platform-tests
[css-anchor-position] Limit position options list to five
Limits the amount of excess layout work required for trying options.
Five is the lower cap for position options allowed by the spec.
Bug: 40279608
Change-Id: Iefdf2d97fbf6fcbcc0f1e53ead545e1c975d473a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5372723
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1273299}
--
wpt-commits: 299e58e05e4d9a937bcf904d76097f3a9cbcab5b
wpt-pr: 45106
Automatic update from web-platform-tests
Reland "text-box-trim: remove inline box tests (tentatively)"
This is a reland of commit b42e5ff036c53862314fd556281d3e6c601db784
text-box-trim-half-leading-block-box-001.html's reference file was
set to inline box's by mistake, and this reland fixes the issue.
Original change's description:
> text-box-trim: remove inline box tests (tentatively)
>
> The specification is not updated yet, and it is not that clear to us
> which edges could be cut in these cases.
> Since we do not plan to implement the text-line-edge? property for
> now, I'd like to remove these tests to avoid confusion.
>
> Bug: 40254880
> Change-Id: I08af3d3806e4e49a9e46de0f85271fb995259bbf
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5360144
> Commit-Queue: Lingqi Chi <lingqi@chromium.org>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1271417}
Bug: 40254880
Change-Id: Ie2c1821c37c838f81bccbe51c6d15864f8550462
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5366868
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1273240}
--
wpt-commits: 309231a7f3e900d04914bc4963b016efd9989a00
wpt-pr: 45076
Automatic update from web-platform-tests
Revert "Add HandleInvokeInternal on HTMLDialogElement" (#45103)
This reverts commit 9eab271e13b1698a07ba15a4cf801098c3187d5c.
Suspected to break tests on https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/35487/overview
Reverting the CL in gerrit failed with some error so I'm manually
reverting it.
Bug: 324601159, 1494810
Change-Id: Iabab8870b5c2d8c40865d5e10df2887b6634c433
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5370574
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Nicola Tommasi <tommasin@chromium.org>
Auto-Submit: Christian Dullweber <dullweber@chromium.org>
Owners-Override: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Nicola Tommasi <tommasin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1272680}
Co-authored-by: Christian Dullweber <dullweber@chromium.org>
--
wpt-commits: 0d0f9ccf333f529e145c4c1dbfd8221ade20dc26
wpt-pr: 45103
Automatic update from web-platform-tests
Add new print mode grid overflow test (#45111)
* Add new print mode grid overflow test
This one fails in Chromium but passes in Firefox.
--
wpt-commits: f1adc2b2b78766d0dda7c2aae82e2e6fbc2b8b99
wpt-pr: 45111
Automatic update from web-platform-tests
[css-scroll-snap-2] Switch snapchanged to updated SnapEvent interface
This patch makes snapchanged fire SnapEvents based on the updated[1]
SnapEvent interface which supplies exactly one snap target per axis.
We detect that the snap targets of a SnapContainerData has changed by
comparing its current target_snap_area_element_ids_ to the element ids
that were most recently used to evaluate snapchanged. This requires
that if a snap container is snapped in both axes but is then scrolled
in only one axis, it needs to remember what it was snapped to in the
other (unscrolled) axis - previously, we simply forgot what we were
snapped to in the unscrolled axis.
prefer-common-to-both-axes.html had to be modified because remembering
what we are snapped to in the unscrolled axis affects the choice of
snap targets when there is a layout change resulting in the targets
along each axis not being mutually visible. Currently, chromium handles
this somewhat arbitrarily (This will be adddressed in
crbug.com/329250094) This patch gets around this by scrolling in both
axes.
snapchanged-ensures-dom-order.html is deleted because we don't return a
list anymore so we don't need to ensure the order of the list.
[1]https://github.com/w3c/csswg-drafts/pull/9515
Bug: 329111147
Change-Id: I4af884bd58d0517087a8c8960bf7646f3a36ba72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5369681
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1273041}
--
wpt-commits: 2817af77c7e8465130e93b5d4935e0887dd8ea81
wpt-pr: 45109
Automatic update from web-platform-tests
Enable sharedStorage.get() in network-restricted fenced frames.
If the proper flag (kFencedFramesLocalUnpartitionedDataAccess) is
enabled, sharedStorage.get() can now be called in fenced frames.
The call will only succeed if the entire tree rooted at the fenced
frame has disabled untrusted network access, including nested
fenced frames trees.
Bug: 324440086
Change-Id: Ie6788ba6d299a334800ecf11ba90151eaf40f43d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5279221
Reviewed-by: Cammie Smith Barnes <cammie@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Commit-Queue: Andrew Verge <averge@chromium.org>
Reviewed-by: Garrett Tanzer <gtanzer@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1272982}
--
wpt-commits: b83bbdfc87212d5af05a3b0e0dd82c4fdf7031c1
wpt-pr: 44484
Firefox never uses this. TB could use the same approach Firefox uses,
but for now on macOS the sheets become regular modal dialogs, which is
the same as on Windows and Linux.
See bug 1755330 and bug 1737489 for more context.
Differential Revision: https://phabricator.services.mozilla.com/D204209
With this patch
- The line gutter context menu will get displayed on right click of the gutter
- Clicking line gutter should set breakpoints
Note not covered in this patch:-
- Context menu feaures might not work
- Line breakpoints are not showing yet ( this is coming in a future patch)
Differential Revision: https://phabricator.services.mozilla.com/D203210
