Closed Bug 1543099 Opened 6 years ago Closed 6 years ago

Implement Runtime.evaluate

Categories

(Remote Protocol :: CDP, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ochameau, Assigned: ochameau)

References

Details

Attachments

(2 files)

Once bug 1543098 is done and Runtime.executionContextCreated events are sent, we can start implementing Runtime.evaluate and Runtime.callFunctionOn.

https://chromedevtools.github.io/devtools-protocol/tot/Runtime#method-evaluate
https://chromedevtools.github.io/devtools-protocol/tot/Runtime#method-callFunctionOn

Here, I'm suggesting to implement both in the same bug as they are very similar and both are used by puppeteer to implement Page.evaluate.

Priority: -- → P2

I'm scoping this down to implement only Runtime.evaluate as it appears that callFunctionOn can easily be implemented in a followup and brings some additional complexity that would be worth reviewing independently.

Summary: Implement Runtime.evaluate and Runtime.callFunctionOn → Implement Runtime.evaluate
Attachment #9058292 - Attachment description: Bug 1543099 - Implement Runtime.evaluate and Runtime.callFunctionOn → Bug 1543099 - Implement Runtime.evaluate.
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7c074ab51d55 Split browser_runtime_executionContext into multiple functions r=remote-protocol-reviewers,ato https://hg.mozilla.org/integration/autoland/rev/6c9b27fd6233 Implement Runtime.evaluate. r=remote-protocol-reviewers,ato
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Priority: P2 → P1
Component: CDP: Runtime → CDP
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: