Andrey Lushnikov
Andrey Lushnikov
> The page.waitForSelector with {visible: true} should have found and returned the visible element on the page. @razorman8669 Ok I see what you mean here. Indeed, the behavior is somewhat...
> Cause i hope to reduce the number of requests @Syuking Does it hit performance of the page loading in your tests?
@joanrieu thank you for filing this issue with your findings: I've spent 2 weeks debugging this before figuring out the right words to google and stumbling upon this issue.
@furstenheim this is interesting. Can you please share your usecase?
@furstenheim this looks very reasonable; once #2812 lands we'll add this one as well.
> If necessary I could write up the code and the tests I'd be happy to review a PR! Please make sure to add reference to https://developer.chrome.com/extensions/content_scripts when explaining isolated...
(cross-posting from https://github.com/GoogleChrome/puppeteer/pull/2829#issuecomment-418479798) I've played with this for a while. A few observations: - execution contexts per se are not very handy. Once I have an isolated world, I want...
Once we have isolated worlds, we should push certain PPTR functions to the clean isolated world. Another example of this is #3327: the `page.select` method is currently implemented in page...
@schelkun might be many reasons: chromium bug, OOM, memory corruption etc.
@bahattincinic I don't think this has something to do with the issue. Would you mind filing a new issue with some details, e.g. your pptr version and chrome version?