-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async JSHandle
prepare
#1365
Async JSHandle
prepare
#1365
Conversation
0b09ecb
to
3523f93
Compare
72377f7
to
1982d55
Compare
3523f93
to
76fa23c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woohoo! Less panics! Nice work.
common/frame_manager.go
Outdated
for _, child := range frame.ChildFrames() { | ||
m.logger.Debugf("FrameManager:removeFramesRecursively", | ||
"fmid:%d cfid:%v pfid:%v cfname:%s cfurl:%s", | ||
m.ID(), child.ID(), frame.ID(), child.Name(), child.URL()) | ||
|
||
m.removeFramesRecursively(child) | ||
if err := m.removeFramesRecursively(child); err != nil { | ||
return fmt.Errorf("removing child frames recursively: %w", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this clash with the error in removeChildFramesRecursively
? It might make debugging difficult. Could this error instead be changed to removing frames recursively
?
Then there's the error below when calling frame.detach
, which i think could change to detaching frame
.
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, fixed in 736e87e.
76fa23c
to
736e87e
Compare
What?
Prepare
JSHandle
to be async by turning panics into errors.Why?
JSHandle
to async.Checklist
Related PR(s)/Issue(s)
#1303