When Loop is mentioned below, it means the use of Loop in the built-in conversation window, not the separate standalone web-page. Firm privacy requirements: - When a user is active in Loop, Firefox will be using the Camera/Microphone. The user should be able to: a) know that Firefox is using the camera/microphone, e.g. if Firefox is minimised/behind another app. ---> currently the global controls are used b) know that it is Loop that is using the camera/microphone. ---> currently this is the permission hangers on the conversation windows c) find the window that Loop is active in (even if its minimised). ---> You can currently do this from the global indicators - The user should be easily able to stop sharing devices If the permission icons weren't there, this is basically "exit conversation" currently. However, in the future model of starting with text/tab-sharing only, then I think this will need to change. - The user should have an easily recognisable/discoverable way to stop sharing devices (see comment 8) - The URL bar cannot be used for indicators, due to the potential confusion of the user thinking the website has gained access, when in fact it is only Hello that is using the devices. Other requirements - We need to be able to change the active device whilst in a call. As Adam said in comment 6, the permissions prompts are currently being worked on as a way to do this. We could potentially have some specific Hello UI to do this, but technically I don't know how feasible it would be at the moment. - The user shouldn't be able to mess themselves up. For example, currently stop sharing leads to an ongoing call with broken UX.
From bug 1214215 comment 4, we want to remove the orange tab sharing and video sharing indicators from the conversation window. An initial look points to changing browser code outside of browser/components/loop Not strictly dependent on bug 1214215.
Summary: Remove conversation window indicators for tab sharing and video sharing → Remove conversation window orange indicators for tab and sharing
Summary: Remove conversation window orange indicators for tab and sharing → Remove conversation window orange indicators for tab and video sharing
We need more detailed consideration of this. Firstly we should probably have some folks consider any privacy aspects. Secondly the existing global controls for "control sharing" currently redirect to the pop-up that is underneath the orange icons, so we would need something to replace that. I'm not against removing them, but I think its a little more complicated than just hiding thr buttons.
Ok, right now we have two buttons that perform the same action (or at it least they should). From one side, we have this little orange indicator on the top bar of the conversation window and, on the other side, we have the camera/microphone controls. With the camera and microphone controls in the conversation window, users should be able to turn on/off their camera and microphone so no other button/icon should be needed to control that. What I'm saying is that the best we could do is to remove that orange indicator and replace its functionality by the camera/microphone controls that were specially thought for that. No need to have duplicates.
That's true and reasonable, but it doesn't address what happens with the global controls for finding the window/tab that's sharing the camera/microphone.
I don't thinks that's an issue since we're planning to have that blue toolbar always present. To me, it makes no sense keeping that orange indicators. Plus, if we are worried about where to place the browser permissions button, it should be placed on the left side of the URL bar. Taking into account how these indicators behave right now (specially the video permissions one), I definitely think we should get rid of them asap.
(In reply to Pau Masiá [:Pau] from comment #4) > I don't thinks that's an issue since we're planning to have that blue > toolbar always present. To me, it makes no sense keeping that orange > indicators. Plus, if we are worried about where to place the browser > permissions button, it should be placed on the left side of the URL bar. To me, that could confuse the user into thinking that the site has gained access when it is only Hello using it. Adam: Do you know who's likely to be able to advise us on the privacy aspects of potentially removing these icons from the conversation window toolbar and the global toolbar just for built-in Hello?
(In reply to Mark Banner (:standard8) from comment #5) > Adam: Do you know who's likely to be able to advise us on the privacy > aspects of potentially removing these icons from the conversation window > toolbar and the global toolbar just for built-in Hello? Given that this is a clear security issue, I think that would be Richard Barnes. I'll offer my two cents: this conversation is confusing the permissions controls with the stream controls. Mute/unmute is a very different set of operations than grant permission/revoke permission. The user needs to be able to do both. Actually, strike that: the user MUST be able to control permissions. Mute is more of a "pretty important nice-to-have." Finally, I'll mention that the platform team is presently working on a way to switch devices, and I'm pretty sure it's going to hang off the permissions icon. So, even if the proposal in this bug passes security muster -- and I don't think it will -- you'll be a sad panda if you remove this control, since leaving it in will get you device control in Hello for free.
Flags: needinfo?(adam) → needinfo?(rlb)
I'm a little unclear on precisely what is being proposed here. It would be helpful if someone could post a screenshot of the current UI and an explanation of the changes from that? As a general rule, anything that makes it less clear what is being shared would be a negative. Likewise, anything that is different for Hello from the normal UX is likely to lead to confusion.
Flags: needinfo?(rlb) → needinfo?(edilee)
I grabbed the screenshot of the proposed design from http://people.mozilla.org/~sfranks/Hello/Firefox%20Hello%20Link%20Generator.png
The controls were accidentally not included, but I'm not sure this window is the place for these controls anyway. The conversation window is going away eventually when we move to a sidebar, so the placement of those controls will need reevaluating anyway. Is it not clear enough to show the icons next to the control center icon in the URL Bar? NIing Phlsa here as I believe he has looked into this before.
(In reply to Sevaan Franks [:sevaan] from comment #12) > Is it not clear enough to show the icons next > to the control center icon in the URL Bar? Those indicate that the site has access to the camera (which isn't the case here – Hello is using it). I don't think there's much value in keeping the indicators in the Hello window (other than perhaps the opportunity to switch devices when that lands). The security risk is much lower, since Hello is part of Firefox. As for the global indicators that just switch to the tab, Hello provides its own mute/close/camera mute controls which make more sense in that context.
Ok, I've summarised the discussion in the user story to put together a list of requirements that I think apply to the current UX and should apply to the next iteration of the UX. If there's any you think are wrong/incorrect, please highlight. If we can get a UX design that we think meets those requirements, then I think we could bring people together to discuss and confirm before we move forward with the implementation.
User Story: (updated)
Whiteboard: [needs agreed UX]
The functionality and description of the icons reminds me very much of Checkboxes that Kill: http://limi.net/checkboxes-that-kill/
I couldn't agree more, Ian.
I don't think we have to keep the indicators/drop-downs in their current form, that's not what I'm suggesting. I think we need to come up with something that meets the requirements (or is close to) and doesn't allow the user to mess up their experience.
Whiteboard: [needs agreed UX] → [needs agreed UX][akita-todo]
Whiteboard: [needs agreed UX][akita-todo] → [needs agreed UX][todo-akita]
Whiteboard: [needs agreed UX][todo-akita] → [needs agreed UX][akita-todo]
Whiteboard: [needs agreed UX][akita-todo] → [needs agreed UX][todo-akita]
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.