Should we deprecate no-focus-change?

[youennf]

We started discussing deprecation of no-focus-change in #263.
We should further investigate and come to a conclusion on this.

[eladalon1983]

I think my main argument[0] for retaining this value is that, as currently defined, it is potentially useful for accessibility-conscious applications. I suspect[1] that people using screen readers find it challenging when the active window on the screen changes. The reader needs to announce this, read out the new fields available, etc.

• When such a user is on Chrome-on-Windows, they might prefer to keep the capturing application focused, because that's what they last interacted with and had read out to them.
• When such a user is on Safari-on-macOS, I imagine[2] the macOS media-picker performs some read-out that makes the user feel like the new window is in focus. When such users configure the Web app for a11y, the app might wish to request divergent behavior depending on the platform, and this might be a good way to achieve it.

---

[0] The others arguments mostly being about having to check how much havoc this would wreak on existing applications before committing to a deprecation.
[1] Let's pull someone more experienced in these matters to verify.
[2] Am I wrong?

[youennf]

We now have four possible values:

• focus-capturing-application
• focus-captured-surface
• no-focus-change
• setFocusBehavior not called at all

The last two may be equivalent in that refocusing is limited as much as possible.
In that case, no-focus-change is not really useful, and we should probably mention what the intent is for the case of setFocusBehavior not called at all.
We can also keep setFocusBehavior not called at all totally unspecified, in which case no-focus-change has some value.

[eladalon1983]

The last two may be equivalent in that refocusing is limited as much as possible.

I don't think the spec mentions a default value, so they're not equivalent in theory.
Chrome's default behavior is to focus, so they're not equivalent in practice. (Or not equivalent across all implementations, to be more exact.)

We can also keep setFocusBehavior not called at all totally unspecified, in which case no-focus-change has some value.

That's my preference atm.