1666284 - Determine if the indicator needs to be in the "Window" list on macOS

Status: NEW

(Firefox :: Site Permissions, task, P3)

Description

[Mike Conley (:mconley) (:⚙️)]

I believe we intentionally chose to put the new indicator in the macOS Window menu for accessibility reasons. This happened in bug 1643545, but perhaps having the indicator be keyboard selectable is sufficient, and we don't need it in the list.

jteh, what do you think?

Comment 1

[James Teh [:Jamie]]

To clarify, can you still get to the indicator using the keyboard in the same way even when it's not in the window list?

If so, that seems reasonable to me; the objective here was to make sure it was keyboard accessible. NI Marco in case he has other thoughts, since he's more familiar with mac conventions than I am.

That said, what is the motivation for wanting to remove this from the window list? Does this negatively impact other users?

Comment 2

[James Teh [:Jamie]]

Mike, I was discussing this with Marco and he noted he couldn't get the indicator to appear. I just tested myself on Windows and I can no longer get it to appear either! I tested with this test page and also Jitsi meet. I see there's a privacy.webrtc.hideGlobalIndicator pref which defaults to false. I tried flipping that to true and restarted, but I still can't get it to appear. Any ideas?

Comment 3

[Mike Conley (:mconley) (:⚙️)]

Hi Jamie,

Sorry to get back so late to this. Now that I've got my review queue under control, I'm finally burning my way through needinfos.

So the indicator changed behaviour recently, where it only shows if the user is sharing a display over WebRTC. So in order to get the indicator to open, you'll need to choose to share either an application window, or a screen.

You can also potentially use this demo site to test: https://www.webrtc-experiment.com/getDisplayMedia/

Comment 4

[Marco Zehe (:MarcoZ)]

I just tested this, and the only way I could actually get to it was through VoiceOver's window menu. I got the indication from VoiceOver that there was a new window when I started to share my screen in Google Meet. But there was no doorhanger, F6 didn't get me there, and neither did tabbing. If it behaved like any other doorhanger, it would be sufficient, too, and not needed to be in the window list. But if this is meant to be special, the window list seems like the best option.

Comment 5

[James Teh [:Jamie]]

Based on Marco's feedback, it looks like the window list is the only way to access this for a keyboard/VoiceOver user. Mike, is there some other way to access this via the keyboard? (Comment 0 suggested there might be, but if so, we don't know what it is.) If not, I'd say it needs to stay in the window list and we should wontfix this bug.