New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong modal renderization #29459
Labels
stage: needs information
Not enough info to reproduce the issue
Comments
@ferrange Are there any errors in the Cypress browser that aren't shown in an outside browser? Also make sure you're using as close to the same browser type and version as possible. Without a way for us to run and see the issue, there's not much we can do to track down the root cause unfortunately. |
jennifer-shehane
added
the
stage: needs information
Not enough info to reproduce the issue
label
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
In a specific webpage, when we select an asset and we press on donwload, a modal is displayed showing more options than it should, like if it was loading all the possibilities without having the js logic in consideration.
As you can see, there are no extra flags checked
Desired behavior
As it is when navigating through the browser or any other framework, when we perform the same actions, the modal is displayed showing only the options it has to:
If we check the "Dynamic Rendition(s)" flag, then more options are displayed:
Here you can see how the property display swaps from none to block when checking and unchecking the flag:
Test code to reproduce
No need of test code to reproduce, it happens aswell when accessing to this webpage by a cy.visit() and then navigating "manually" through cypress interface using npx cypress open.
Due to confidenciality purposes I can not share the website, all I can say is it's based on the Adobe CRM, named Adobe Experience Manager
Cypress Version
13.6.4
Node version
v21.2.0
Operating System
Windows 10 Enterprise 22H2
Debug Logs
No response
Other
@victortfe
The text was updated successfully, but these errors were encountered: