Cypress Studio Assertions Submenu Not Expanding

[SachinJadeja]

Current behavior

When using Cypress Studio to generate test cases, the assertion submenu (e.g., "have text") does not expand when clicked. Other assertions (like "be visible") appear to work fine, but the submenus for specific assertions do not open.

Desired behavior

Clicking on an assertion submenu (e.g., "have text") should expand to show further options.

Steps to Reproduce

1. Open Cypress Test Runner.
2. Start Cypress Studio and generate a test case.
3. Select an element and attempt to add an assertion.
4. Click on the "have text" submenu.
5. Observe that the submenu does not expand.

Test code to reproduce

No test code since this happened in Cypress Studio

Cypress Version

14.0.0

Node version

v23.5.0

Operating System

macOS Sequoia Version 15.2

Debug Logs

Other

[jennifer-shehane]

@SachinJadeja Thanks for reporting. Can you confirm whether this is a mew issue in 14.0.0? That is, if you downgrade to 13.17.1, does this issue still occur?

[SachinJadeja]

@jennifer-shehane this issue also occurs on v13.
FYI this issue didn't occur in v13 few months ago.

[jennifer-shehane]

@SachinJadeja Hi, we've actually been unable to reproduce this behavior. I brought up the Real World App to test the same element within Studio on 13.x and 14.0.0. Can you give some more information so that we can track the issue down?

1. Which test/view are you running exactly within RWA?
2. Which browser are you launching when this happens?
3. Could you send a video recording of the behavior? That might give us some clues we're missing.

[SachinJadeja]

@jennifer-shehane Thank you for your prompt response.
1. I was trying to create an end-to-end test using Cypress Studio by navigating to a website, right-clicking on an element, and selecting the proper assertion.
2. This behaviour occurs in Chrome, Electron, and Firefox.
3. I’ve attached a Loom recording for reference.

Let me know if you need any additional details. Thanks.

[jennifer-shehane]

@SachinJadeja Can you open devtools console and share if there are any errors appearing in there? Also disable any extensions (although I doubt that's it with it happening in multiple browsers).

[SachinJadeja]

@jennifer-shehane This issue appears to be occurring specifically in certain modal components of our product. You can either deprioritize it or close it if needed.

I really appreciate you taking the time to look into this. Thanks!