fix(service): do not drain a page a native session does not have

[vishnuv688]

What & why

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Polish (an improvement to an existing feature)
• Breaking change (existing behavior changes for users)
• Documentation
• Internal (build, CI, dependencies, tooling)

Packages touched

• shared (types and contracts)
• core (framework-agnostic capture/reporting)
• elements (published element/snapshot API — @wdio/elements)
• service (WebdriverIO adapter)
• nightwatch-devtools (Nightwatch adapter)
• selenium-devtools (Selenium adapter)
• selenium-devtools-py (Selenium Python adapter)
• backend (server)
• app (UI)
• script (page-injected runtime)
• trace (Trace mode)

Notes for reviewers

Screenshots / recordings

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the previous mobile-web trace-loss finding is fully addressed and no new actionable failures were established.

Summary

• Native app sessions now avoid page-side trace, snapshot, settling, performance, and viewport operations that require a document.
• Appium browser sessions retain DOM trace capture, web snapshots, document settling, and page viewport metadata.
• Tests cover native Android/iOS, Appium Chrome/Safari, vendor capability bags, action snapshots, viewport selection, and trace drains.
• The previous finding is fully fixed: Appium browser sessions are no longer excluded from page drains.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[WebdriverIO session] --> B{Appium session?}
  B -- No --> C[Desktop web capture]
  B -- Yes --> D{Capabilities name a browser?}
  D -- Yes --> E[Appium mobile-web capture]
  D -- No --> F[Native-app capture]
  C --> G[DOM drains, web snapshots, page viewport]
  E --> G
  F --> H[Skip DOM drains and use native page source/window size]

Loading