Skip to content

iOS 27: a floating-bar container that ends at a JS tab bar marks the whole tab covered #4365

Closed

Description

@TanmayOG

On iOS 27.2, the Bottom Tabs screen of tester-army/e2e's mobile benchmark (apps/mobile-benchmark, a React Native app with a JS tab bar) publishes two _UIFloatingBarContainerView nodes (Toolbar). One covers the whole viewport, (0, 0) 402x874. The other ends where the JS tab bar starts, (0, 0) 402x791. The first is exempt as viewport chrome. The second is not, so every node above the tab bar comes back interactionBlocked: 'covered' with coveredBy "Toolbar", the tab's content (home-tab-content) and the header included. Nothing is drawn over them.

press id="complete-action-button" on the Actions tab is refused with target_covered. tester-army/e2e's bottom tabs act inside the last tab fails on that tap on 27.2 with main, and 0.21.36 refuses the same tap. On iOS 26.5 the same screen has no covered nodes.

Environment

  • agent-device main 093341a60, and 0.21.36 from npm
  • iPhone 18 Pro simulator, iOS 27.2 (24B8117), Xcode 27.2 (27B52)
  • macOS 27.0.1, Node 25.5.0
  • App: the e2e benchmark Release build (dev.e2e.benchmark), Bottom Tabs scenario

Command and output

snapshot -i --json on the Home tab, summarised:

ref type label rect mark
e2 StaticText Home 177,71 47x20 covered by Toolbar
e3 StaticText Home (home-tab-content) 173,422 55x24 covered by Toolbar
e4 StaticText Go to the Actions tab and… 53,454 297x16 covered by Toolbar
e5 Toolbar Toolbar 0,0 402x791
e6 Button Home, tab, 1 of 3 0,791 134x49
e7 Button Feed, tab, 2 of 3 134,791 134x49
e8 Button Actions, tab, 3 of 3 268,791 134x49
e9 Toolbar Toolbar 0,0 402x874

press 'id="complete-action-button"' --platform ios --json on the Actions tab (logPath and diagnosticId left out):

{
  "success": false,
  "error": {
    "code": "COMMAND_FAILED",
    "message": "Selector id=\"complete-action-button\" is covered by another visible element and cannot be tapped safely",
    "hint": "Covered by the toolbar \"Toolbar\" at (0, 0 402x791). Dismiss or close that element, scroll the target clear of it, or inspect with snapshot/screenshot before retrying.",
    "details": {
      "reason": "target_covered",
      "selector": "id=\"complete-action-button\"",
      "ref": "@e4",
      "interactionBlocked": "covered",
      "coveredBy": { "kind": "toolbar", "label": "Toolbar", "rect": { "x": 0, "y": 0, "width": 402, "height": 791 } },
      "dispatched": "no"
    }
  }
}

Cause

Expected

  • On this screen, snapshot -i marks nothing covered by the 402x791 container (today 3 of 9 on Home, 2 of 8 on Actions).
  • press id="complete-action-button" taps.
  • A toolbar or bar drawn over content keeps covering it.

Proposed fix

Let the full-viewport check also accept the viewport above a bottom bar, that is, a sibling that starts at the container's bottom edge, below the viewport's middle. A bar drawn over content ends above the middle and keeps covering. With that change, the same screen comes back 0 of 9 covered, the press lands, and the e2e test passes. I have it built with tests and can open the PR if this direction works for you.

Found while working on e2e-inc/e2e#1644, which now reads a covered node as hidden, so on iOS 27 this mark also fails toBeVisible on that screen.

Activity

  1. thymikee commented on Nov 11, 2026

    @thymikee
    Member

    Triage: bug; actionable without more input from you. The occlusion scan exempts a _UIFloatingBarContainerView that spans the viewport, but not one that ends where a JS tab bar starts. On iOS 27.2 that second container marks every node above the tab bar covered. Thanks for the node table and the 26.5 comparison. An agent can pick this up.

  2. thymikee commented on Nov 11, 2026

    @thymikee
    Member

    An agent is picking this up; the PR will link here.

  3. thymikee commented on Nov 11, 2026

    @thymikee
    Member

    A fix is up in #4405. A _UIFloatingBarContainerView that ends where a row of tab buttons or tab items starts now counts as chrome, so content above the tab bar is no longer marked covered. A single bottom button or a Cancel/Confirm row still counts as a cover. We have no iOS 27.2 simulator here, so the benchmark Bottom Tabs screen hasn't been run against it. If you can check that branch, please post snapshot -i --json from the Home tab and the result of press 'id="complete-action-button"' on the Actions tab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions