Closed Bug 1987605 Opened 4 months ago Closed 4 months ago

Clarify behavior of "isMobile" argument of "browsingContext.setViewport" command on the spec level and check RDM implementation

Categories

(Remote Protocol :: WebDriver BiDi, task, P2)

task
Points:
3

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Sasha, Assigned: Sasha)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [webdriver:m17])

In order to implement "isMobile" argument of "browsingContext.setViewport" command, which should mimic "mobile" argument in CDP "Emulation.setDeviceMetricsOverride" command, we have to clarify first what is the expected behavior to write the specification of it and evaluate if some parts of RDM implementation might be reused here.

Points: --- → 3
Priority: -- → P2
Whiteboard: [webdriver:m17]
Assignee: nobody → aborovova
Status: NEW → ASSIGNED

What I could find out about requirements in Emulation.setDeviceMetricsOverride :

Playwright seems to be expecting for their isMobile to only require:

  • touch to be enabled (already extracted in the separate property);
  • viewport meta tags to be applied;
  • overlay scrollbars.

The future work will be split into separate APIs for touch, viewport meta tags and overlay scrollbars.

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.