puppeteer/test
Andrey Lushnikov 6512ce768d
fix(Frame): postpone evaluations until execution context gets created (#1415)
In Blink, frames don't necesserily have execution context all the time.
DevTools Protocol precisely reports this situation, which results in
Puppeteer's frame.executionContext() being null occasionally.

However, from puppeteer point of view every frame will have at least a
default executions context, sooner or later:

- frame's execution context might be created naturally to run frame's
  javascript
- if frame has no javascript, devtools protocol will issue execution
  context creation

This patch builds up on this assumption and makes frame.executionContext()
to be a promise.
As a result, all the evaluations await for the execution context to be created first.

Fixes #827, #1325

BREAKING CHANGE: this patch changes frame.executionContext() method to return a promise.
To migrate onto a new behavior, await the context first before using it.
2017-11-18 16:27:52 -08:00
..
assets Test: add tests to cover clicking checkbox (#1125) 2017-11-07 20:38:22 -08:00
golden fix(ElementHandle.screenshot): account for scroll (#1323) 2017-11-10 16:02:52 -08:00
server [api] Implement page.authenticate method (#729) 2017-09-11 16:32:13 -07:00
diffstyle.css Implement FrameManager 2017-06-21 14:11:52 -07:00
frame-utils.js Remove promise jsdoc (#641) 2017-08-31 17:58:07 -07:00
golden-utils.js chore(doclint): move doclint tests expectations into test folders (#932) 2017-10-02 11:37:16 -07:00
test.js fix(Frame): postpone evaluations until execution context gets created (#1415) 2017-11-18 16:27:52 -08:00