Brian Mann

Okay let me clear up a few things. When we say GUI mode we're talking about launching cypress from `cypress open`. In that mode the tests never "complete" and you...

Also at this very moment you could do this trick here: https://github.com/cypress-io/cypress/issues/300#issuecomment-321587149 That will get all console.log's to show up in the command log, which will stringify and print their...

I opened a couple new issues to do what you're asking with exporting the `console` output, and some improvements to the debugging the driver.

If you want to iterate without it close, just open up Electron in the GUI. Just select that browser instead of Chrome. You may see the same issue. As I...

Related to #699 and #700. Those will land pretty soon and should help alleviate these problems.

Is the `iframe` same domain or cross domain? We can pretty easily add same domain iframe support. Cross domain will take a lot more work. The difference will likely be...

Cypress actually injects to forcibly enable it to access same domain `` and even sub-domain `` but there is an artificial limitation in the driver code where it get's confused...

@harz87 the `braintree` iframes you're referring to are cross origin frames right? If that's the case you'll need to [disable web security](https://on.cypress.io/guides/web-security) before being able to access them. After you...

EDITED: to show using proper Cypress commands. ```js .get('iframe.stripe_checkout_app') .then(function ($iframe) { const $body = $iframe.contents().find('body') cy .wrap($body) .find('input:eq(0)') .type('4242424242424242') cy .wrap($body) .find('input:eq(1)') .type('1222') cy .wrap($body) .find('input:eq(2)') .type('123') }) ```

We don't show content in iframes when reverting to a snapshot (nor will we ever do that). However we will eventually support targeting DOM elements inside of iframes.