New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 650890 link

Starred by 1 user
Status: Fixed
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[DevTools] Runtime.evaluate with asyncAwait:true doesn't trigger callback for resolved promise

Project Member Reported by kozyatinskiy@chromium.org, Sep 27 2016 
InspectorTest.sendCommand("Runtime.evaluate", { expression: "Promise.resolve(239)", awaitPromise: true }, (r) => console.log(r));

This command should call callback right after execution.

Comment 1 by kozyatinskiy@chromium.org, Sep 27 2016 

It was fixed by: https://codereview.chromium.org/2371773004/

[inspector] run microtasks after async Runtime.evaluate

If promise was resolved before adding handler in Runtime.evaluate method then this callback won't be called. We need to run microtasks after adding handlers.

R=dgozman@chromium.org,alph@chromium.org
BUG= chromium:650890 
Committed: https://crrev.com/ff135975b0078aac1cc64415033ec721401ad461
Cr-Commit-Position: refs/heads/master@{#39793}

Comment 2 by kozyatinskiy@chromium.org, Sep 27 2016

Status: Fixed (was: Assigned)

Comment 3 Deleted

Comment 4 by kozyatinskiy@chromium.org, Sep 27 2016

Summary: [DevTools] Runtime.evaluate with asyncAwait:true doesn't trigger callback for resolved promise (was: [DevTools] Runtime.evaluate with asyncAwaitLtrue doesn't trigger callback for resolved promise)
►

Sign in to add a comment