Benoît

Indeed, it seems they have put a silent captcha. Looks like it'll be hard to bypass. Sorry guys, I don't think we'll be able to login anymore.

Ah, yes. I'll think about it. I could do something like displaying the instructions, and then a prompt for the session id instead of a prompt for username/password.

Thanks a lot for this pull request! I just tried to install it on an empty wheezy image ([from here](https://people.debian.org/~aurel32/qemu/i386/)). The package building and installation is working just fine, but...

Ha, same issue at the same time :-)

For your information, my workaround looks like: ```js page._frameManager.on("lifecycleevent", frame => { if (frame._lifecycleEvents.has("networkIdle") && !frame._lifecycleEvents.has("load")) { // Mixed content error } }); ```

For those who are looking for a quick solution, this is how I resolved it in graphql 1.1: ```python import logging from graphql.execution.executors.asyncio import AsyncioExecutor from promise import Promise logger...

After investigation, it seems that this issue is caused by macOS FSEvent notifying of a change on `target/wasm-pack/xxx/index.js` even if this file is being watched *after* the change. In fact,...

See https://github.com/import-js/eslint-plugin-import/pull/2511

Please provide more information, as requested in [the bug report template](https://raw.githubusercontent.com/BenoitZugmeyer/eslint-plugin-html/master/.github/ISSUE_TEMPLATE/bug-report.md) you saw when opening the issue.

This is a very good suggestion and I would be in favor of exploiting those new APIs and remove a bit of dirty monkey patching from my plugin 😃 But...