You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are telling developers to use traverse::end to evaluate their scripts. The problem is that with the changes in #494 with jsdom we could actually evaluate at the beginning instead of waiting at the end to save a few seconds. That is not the case with chrome where we will be interfering with the page.
The proposal is to create a new event canevaluate (or similar) that will be fired by the connectors when it is best for them to evaluate. jsdom will fire it sooner than chrome in this case.
What do you think @sonarwhal/contributors ?
The text was updated successfully, but these errors were encountered:
Initial comment: #494 (comment)
Right now we are telling developers to use
traverse::end
toevaluate
their scripts. The problem is that with the changes in #494 withjsdom
we could actuallyevaluate
at the beginning instead of waiting at the end to save a few seconds. That is not the case withchrome
where we will be interfering with the page.The proposal is to create a new event
canevaluate
(or similar) that will be fired by the connectors when it is best for them toevaluate
.jsdom
will fire it sooner thanchrome
in this case.What do you think @sonarwhal/contributors ?
The text was updated successfully, but these errors were encountered: