Closed Bug 1938055 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 49757 - [LoAF] Set sourceCharPosition for the invoke-type resolve-promise

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox135 fixed)

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 49757 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/49757
Details from upstream follow.

Joone Hur <joonehur@microsoft.com> wrote:

[LoAF] Set sourceCharPosition for the invoke-type resolve-promise

The script entries of LoAF for the promise-resolve invoker type do not
provide sourceCharPosition. This CL enables the provision of the source
position.

  • Introduced CapturePartialSourceLocationFromStack(v8::Isolate*) to
    retrieve both URL and starting character position of the currently
    executing script.
  • Added LongAnimationFrameSourceCharPosition runtime flag.

Bug: 381529126
Test:

  • external/wpt/long-animation-frame/tentative/loaf-source-
    location.html
  • external/wpt/long-animation-frame/tentative/loaf-source-location-redirect.html

Change-Id: I481a62d8eb4a5649fdddcff5b657d442335e8725
Reviewed-on: https://chromium-review.googlesource.com/6060398
WPT-Export-Revision: 206fc271d7233af452633267765d1af9925dcc5b

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 5 subtests

Status Summary

Firefox

ERROR: 2

Chrome

OK : 2
PASS : 14
FAIL : 3

Safari

ERROR: 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/825a7ea97490 [wpt PR 49757] - [LoAF] Set sourceCharPosition for the invoke-type resolve-promise, a=testonly
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.