When running a test with cypress 4.6.0, I am noticing that that address bar is showing when the test starts and then disappearing shortly after.
I am also noticing the view port is resizing and not showing the whole application while the tests run through. I was on version 4.4.1 prior to uploading (didnt see these issues), so I am not sure if this issue was present on 4.5.0.
I would expect the address bar would always show during a test and that the page doesnt resize/ stays the same size during the test run.

4.6.0
mac (high sierra 10.13.6)
chrome and edge browsers (did not try others)
+1 it's gone for me as well
I bet this is due to https://github.com/cypress-io/cypress/pull/7203
@jennifer-shehane would this be slated for the next release?
Yeah, I can see the same issue with v4.6.0 whereas 4.5.0 looks good.
OS: macOS Mojave 10.14.6
Browsers: Chrome, Edge, Firefox and Electron
Noticed this happens when Cypress scrolls to an element that is not visible within the specified viewport, although it scrolls to the element correctly.
I was able to recreate this with the following code. I also have to run this code in combination with resizing the main browser window to touch either the width/height of the AUT iframe. So if my browser window is really maxed out - you won't see it.
index.html
<html>
<body>
<p style="height: 2000;">Aenean lacinia bibendum nulla sed consectetur.</p>
<footer>Aenean lacinia bibendum nulla sed consectetur.</footer>
</body>
</html>
spec.js
it('test', () => {
cy.visit('index.html')
cy.get('footer').click()
})

Reverting #7203 fixes the issue. Will go ahead and revert and reopen the other issue this was fixing since this affects more people.
The code for this is done in cypress-io/cypress#7448, but has yet to be released.
We'll update this issue and reference the changelog when it's released.
Released in 4.7.0.
This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v4.7.0, please open a new issue.
Most helpful comment
Reverting #7203 fixes the issue. Will go ahead and revert and reopen the other issue this was fixing since this affects more people.