Conditional Focus

[eladalon1983]

Request for position on an emerging web specification

• WebKittens who can provide input: @youennf

Information about the spec

• Spec Title: Conditional Focus
• Spec URL: https://www.w3.org/TR/screen-capture/#dom-capturecontroller-setfocusbehavior
  • Generally, it's in: https://www.w3.org/TR/screen-capture/#dom-capturecontroller-setfocusbehavior
  • The two PRs that introduced this are:
    • https://github.com/w3c/mediacapture-screen-share/pull/235/files
    • https://github.com/w3c/mediacapture-screen-share/pull/240/files
• GitHub repository: https://github.com/w3c/mediacapture-screen-share/
• Explainer (if not README.md in the repository): https://github.com/WICG/conditional-focus/blob/main/README.md

Design reviews and vendor positions

• TAG Design Review: Conditional Focus (When Display-Capture Starts) w3ctag/design-reviews#679
• Mozilla standards-positions issue: Conditional Focus mozilla/standards-positions#697

[youennf]

The use case is fine.

This API as it currently is defined, is only useful for popup surface selection pickers and does not align well with better OS level picker alternatives like on macOS. The issue is that the API does nothing as soon as the capturing page is no longer focused, which always happens for the macOS picker.
It should not be too difficult to adapt the spec and hopefully the difference will not cause compat issues.
We should probably file an issue about this sooner rather than later.

I would tend to go with 'position support'.

[youennf]

I filed w3c/mediacapture-screen-share#263 and w3c/mediacapture-screen-share#262

[othermaciej]

It looks like our two issues are not fully addressed yet, despite some discussion.

[eladalon1983]

Let me know if you're waiting for me to take some action on either of these.

[marcoscaceres]

Looks like this might not need to be a standards position. There were spec issues filed and can probably be handled at the spec level. @eladalon1983, do you agree?

Looks like Mozilla reached the same conclusion - this shouldn't need a standards position. This is a spec-level issue.

(@youennf was going to send a PR to help close the open issue)

[eladalon1983]

The request for a standards position was filed in conjunction with an intent-to-ship in Chrome 1.5 years ago (link). My naive understanding is that an official position from Apple might not be so actionable anymore, but I could be wrong.