- Issue created by @jessebaker
- ๐ฌ๐งUnited Kingdom jessebaker
Removing [PP-1] - I don't see anything remaining preventing this from being worked on.
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
Funny enough, I just articulated a proposed solution on a related issue: #3492358-21: Provide API to allow component instances to behave differently while being previewed โ .
- First commit to issue fork.
- ๐ฎ๐ณIndia roshni upadhyay
roshni upadhyay โ changed the visibility of the branch 3488598-prevent-more-scenarios to hidden.
- ๐ฎ๐ณIndia roshni upadhyay
roshni upadhyay โ changed the visibility of the branch 3488598-prevent-more-scenarios to hidden.
- ๐ฎ๐ณIndia roshni upadhyay
roshni upadhyay โ changed the visibility of the branch 3488598-prevent-more-scenarios to active.
- Merge request !1019Issue-3488598 Prevent more scenarios in preview โ (Open) created by Unnamed author
- ๐ฎ๐ณIndia sanket.tale
sanket.tale โ made their first commit to this issueโs fork.
- ๐ฎ๐ณIndia roshni upadhyay
Hi,
I've written a Cypress test case for this, and the component renders correctly in the Cypress preview. However, the JavaScript behavior doesn't seem to apply inside the iframe. Specifically, when clicking the link, the alert dialog that normally opens in the actual preview page is not triggered during the Cypress test.
It behaves as expected in the real preview (as shown in the attached video), but not in the Cypress iframe environment.
Do we need to make any additional changes or configurations to ensure the JavaScript inside the iframe behaves the same way during testing? Attach video for the same.