cy.origin should throw an error when block is declared within same-origin context

[AtofStryker]

What would you like?

if a user declares a cy.origin command with the same origin policy as that of the AUT/top, an error should be thrown to prompt the user that this is not needed and ask if the user did this intentionally

Why is this needed?

Currently there is some confusion around cy.origin when using same origin spec bridges to that of top/AUT where no feedback is virtually given. This should give users an actionable error message to guide them in the right direction when using cy.origin

Other

No response

[AtofStryker]

There is one test that I know of that uses same origin spec bridges within the cy-in-cy tests. This will likely need to be changed when these changes go into effect

[cypress-bot]

The code for this is done in cypress-io/cypress#24569, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[mjhenkes]

Released in 11.0.1.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v11.0.1, please open a new issue.