63811e8680
This properly threads through the `executionContextId` to the request reported to the DevTools front-end, similarly to how we already report the `executionContextId` as part of `Runtime.bindingCalled`. Bug: chromium:1231521 Change-Id: I0a003041aedd8ec661d1b07cdddbcd1f2866a99f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3046187 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#75875} |
||
---|---|---|
.. | ||
create-session-expected.txt | ||
create-session.js | ||
debugger-stepping-and-breakpoints-expected.txt | ||
debugger-stepping-and-breakpoints.js | ||
pause-on-console-assert-expected.txt | ||
pause-on-console-assert.js | ||
runtime-command-line-api-expected.txt | ||
runtime-command-line-api.js | ||
runtime-console-api-called-expected.txt | ||
runtime-console-api-called.js | ||
runtime-evaluate-exception-expected.txt | ||
runtime-evaluate-exception.js | ||
runtime-evaluate-expected.txt | ||
runtime-evaluate.js | ||
runtime-remote-object-expected.txt | ||
runtime-remote-object.js |