feat: (multi-domain) adding support for cy.visit in multi-domain

[mschile]

• Closes [Multi-domain]: Handle createDomain then visiting primary domain #19857
• Closes [Multi-domain]: Handle subsequent visits within the same domain #20431
• Closes [Multi-domain]: Handle the first visit witin switchToDomain #19876

User facing changelog

n/a

Additional details

This change supports the following:

• Using cy.visit() within switchToDomain both as the first navigation to a new domain or navigating within the domain
  • Note: relative urls are NOT currently supported
• Using cy.go() within switchToDomain

Details:

• Stability is sync'd in from primary domain to allow the command queue to proceed
• When requesting a change to the iframe src prop in the secondary, a message is sent to the primary to perform that actual change since the secondary does not have access to the $autIframe
• When resolving the url on the backend, the isMultiDomain value is passed along to:
  • prevent the server from updating the remote state with the new origin
  • inject fullMultiDomain for buffered multi-domain responses
• hasVisitedAboutBlank is sync'd between primary and secondary to ensure about:blank is only visited once for the spec

How has the user experience changed?

Users are now able to use cy.visit() within switchToDomain

    it('supports visiting primary first', () => {
      // visit primary that doesn't redirect to secondary
      cy.visit('/fixtures/multi-domain.html')

      cy.switchToDomain('foobar.com', () => {
        // visit secondary
        cy.visit('http://www.foobar.com:3500/fixtures/multi-domain-secondary.html')

        cy.get('[data-cy="dom-check"]').should('have.text', 'From a secondary domain')
      })
    })

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?
• [na] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[chrisbreiding]

Very nice! Besides the few nitpicks, it looks there are some legitimately failing tests that need to be looked into.

[cypress]

---

Test summary

20258 • 0 • 326 • 4 • 5

---

Run details

Project	cypress
Status	Passed
Commit	c5c867d
Started	Mar 7, 2022 6:56 PM
Ended	Mar 7, 2022 7:10 PM
Duration	13:29 💡
OS	Linux Debian - 10.10
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/commands/net_stubbing_spec.ts		5
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
2	network stubbing > intercepting response > can 'delay' a proxy response using Promise.delay
3	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
4	network stubbing > intercepting response > can 'delay' a proxy response using Promise.delay
5	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[mjhenkes]

You've made this look easy :)