w3c / w3c/webdriver

Switch To Window (and possibly other commands) should restore the window if iconified

Open
#1,229 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
HTML
Stars
718
Forks
228
PR merge metrics
No merged PRs in 30d

Description

In chapter 10. Command Contexts, section 10.3 Switch To Window:

Update any implementation-specific state that would result from the user selecting the current browsing context for interaction, without altering OS-level focus.

I'm implementing minimize and maximize, and find myself wondering about weird corner cases. In particular, I can't tell whether Switch to Window would implicitly un-iconify the window of the specified browsing context or not. Since a user couldn't interact with an iconified window, the quoted step above would seem to imply that the associated window should be un-iconified and the relevant tab should be selected. But if this is the case, then the remote end steps should say "restore the window".

If switching to a window does not implicitly un-iconify it, then we run into weird implementation issues where restoring a window may implicitly switch the active tab as well (if the UA can't switch tabs while iconified).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with section 10.3, Switch To Window, and the quoted implementation-specific state requirement in chapter 10. Compare it with the remote end steps and the minimize/maximize behavior described in the issue. Done means the specification clearly states whether switching to an iconified window restores it and how tab selection is handled.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.