[Bug]: Cannot switch to the newly opened tab

[ferry-luo]

English Translation

In the YAML flow below, clicking the 经济活动/收支管理 module opens a new tab. The next step uses aiAct to visit the given URL, but Midscene actually opens the URL in the old tab instead of switching to the new tab.

I could not find any documented field that forces a switch to the new tab. forceSameTabNavigation does not solve the problem I described.

Reproduce link: none.
Reproduce steps: none.

---

Version

- name: 事前申请
    flow:
      - ai: 在左上角找到'经济活动/收支管理'模块，点击它，会出现新标签页。
      - aiAct: 访问这个url，http://192.168.10.166:8085/a-front/expendManegement/advanceApply
      - ai: 在'请选择业务类型'栏目，点'一般经费申请'

实际现象是在旧标签页访问了给定的url。
官网没看到有啥字段可以控制切换到新标签页。forceSameTabNavigation不能解决我描述的问题

Details

Reproduce link

无

Reproduce Steps

。

[xiaoruiliang]

这个问题啥时候能解决呀

[JeongHan-Bae]

I encountered a related issue when running Midscene on Windows.

My YAML flow is roughly:

flow:
  # 确认已登录到主页，并且关键菜单已加载
  - aiAssert: 页面应包含 "系统概览" 和 "生产排程" 等主菜单项
  - ai: 点击 "系统概览" 菜单 (最多尝试3次)
  - sleep: 1000
  - aiAssert: |
      1. 甘特图看板显示：...
      2. 甘特图订单详情包含：...

English translation of the YAML steps:

• Confirm the user is already logged in and the main menu is loaded.
• Assert that the page contains menu items such as “系统概览” and “生产排程”.
• Click the “系统概览” menu (retry up to 3 times).
• Wait for 1 second.
• Assert that the Gantt board and order details are visible.

The tasks are executed with:

npx midscene "./runner/*.yaml" --summary sum.json --continue-on-error --share-browser-context

The login step is implemented in task03.yaml.
task04.yaml contains the navigation and validation steps.

In the replay recording, Midscene clearly identifies the “系统概览” menu item. An orange box appears around the recognized menu button, the mouse cursor moves onto it, and a click action is performed.

However, the click does not trigger navigation.

Although the screenshot shows a gap between the clickable area and the text, the entire section is actually a responsive zone. In practice, clicking this location will reliably trigger the navigation.
Additionally, this element features a light blue hover effect. However, the screenshot displays it as pure white, indicating the hover state was not triggered. The mouse may not have performed any action.

In manual testing, clicking this same button immediately navigates to the expected page without any issue.

In summary, the click positions highlighted in the generated replay report—whether in video or screenshots—are not biased and represent valid locations. However, the mouse may not have actually performed an operation, or the actual click position may differ from what is shown in the report.

Because the navigation never occurs, the subsequent assertion that checks the Gantt chart content fails.

Additionally, after this first failed click, later click operations in the same flow also appear to stop working. For example, interactions that normally do not involve page navigation—such as clicking a date input field—also become ineffective.

In our testing, this behavior consistently appears when login and the subsequent actions are implemented in separate YAML scripts executed sequentially (with --share-browser-context). Under this setup, most of the clicks in the later script fail to take effect.

If the click retry limit is removed, Midscene will keep retrying indefinitely because the expected state change never occurs.