fix: commands not chained off of cy.get() or queries properly error when cy.origin() is not used and the AUT has navigated away from the primary origin

[AtofStryker]

• Closes Testing Library can fails with a cryptic error rather than the expected error in Cy 14 Prerelease #30848

Additional details

While performing the Cypress 14 bug hunt, @jennifer-shehane ran into an issue where this test was failing:

it(`Verify that items under category News are visible, intentionally will fail`, () => {
  cy.visit("https://ca.yahoo.com/")
  
  cy.findByRole("link", {name: 'News'})
      .should("be.visible")
      .click({force: true})
  
  cy.scrollTo("bottom")
})

This has to due with the AUT navigating away from ca.yahoo.com to ca.news.yahoo.com, which before worked OK since we would inject document domain and Cypress could still communicate with the subdomain of the navigated AUT, even though the frame is in a cross-origin (same site) context. Now that we do not inject document domain be default, scrollTo was trying to be run in a cross-origin (same-site) context, which would fail. When Cypress attempts to access parts of the error, it is unable to due to the frame being in a cross-origin context, which throws the Can't set property message of which only has a getter error.

This is no unique to the cy.scrollTo() command. The cy.window(), cy.document(), cy.title(), cy.url(), cy.location() ,cy.hash(), cy.go(), and cy.reload() will throw a similar error in this situation, or return erroneous values as the commands cannot access the AUT. This commands are exceptions because they do not chain off a queryable to run, like .get(), which checks to make sure the command is being run on the correct origin.

To fix this test, the test needs to be:

it(`Verify that items under category News are visible, now will pass`, () => {
  cy.visit("https://ca.yahoo.com/")
  
  cy.findByRole("link", {name: 'News'})
      .should("be.visible")
      .click({force: true})
  
  cy.origin('https://ca.news.yahoo.com', () => {
    cy.scrollTo("bottom")
  })
})

However, the Can't set property message of which only has a getter should not occur in the first place and the user should be prompted on how to fix the issue. To fix this, Cypress should error when the above commands are run when the AUT has navigated away from the primary origin to prompt the user to fix where the command is being run. This gives the user context that they need cy.origin() to run the command correctly.

Steps to test

Either run the sample test with the published binary (only linux built on this PR so if testing on a different machine check out the code and run in global mode against a project with this test) or remove that added code and run the regression tests in actions.cy.ts to see the commands are allowed to run outside the origin context, which is incorrect.

How has the user experience changed?

Now the scrollTo in our described test works correctly.

Before

After

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

cypress    Run #59869

Run Properties:   Passed #59869  •  09b006d33a: fix: make sure scrollTo, window, document, title, go, reload, location, hash, an...

Project	cypress
Branch Review	fix/check_actionability_on_try
Run status	Passed #59869
Run duration	10m 07s
Commit	09b006d33a: fix: make sure scrollTo, window, document, title, go, reload, location, hash, an...
Committer	AtofStryker
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	14
Skipped	0
Passing	810
View all changes introduced in this branch ↗︎

---

Warning

No Report: Something went wrong and we could not generate a report for the Application Quality products.

[ryanthemanuel]

Looks good. Nice work!