[remote-dbg-next] UX: Update styling of USB scanning status in sidebar
Categories
(DevTools :: about:debugging, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Assigned: mcroud)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Comment 6•6 years ago
|
||
Reporter | ||
Comment 8•6 years ago
|
||
Did we get some feedback on the proposed icons?
Wrong bug sorry. Although we should also make a final decision about this, so keeping the need info :)
Please find the agreed upon design attached.
The design will use the Photon "Generic" message bar styling. I have provided some measurements but all the details can be found here: https://design.firefox.com/photon/components/message-bars.html#sizes-and-grid
The message bar should be as wide as the menu buttons above it.
To comply with Photon we should consider keeping the close button, perhaps having the message reappear in the event that the user disables USB.
Reporter | ||
Comment 10•6 years ago
|
||
Thanks Matt!
Some questions before I can close this:
The message is only displayed when USB debugging is disabled. It doesn't turn into "USB enabled" when you enable USB debugging. Is this correct?
Should we have a title with slightly more details? "USB can be enabled by going to the Setup/Connect page". And "Dismiss this message" for the "X"
If user dismisses the message, the message is hidden. Is the message supposed to be displayed again sometime? We can either:
- permanently hide it for the profile
- display it if the user enabled USB debugging since the last time they dismissed the message
- display it when the user restarts about:debugging
- display it when the user restarts Firefox
I think the second option might be a good balance here?
Assignee | ||
Comment 11•6 years ago
|
||
I was merrily answering your questions when it suddenly occured to me...
Attached is a quick rough I made of where the Setup page is currently heading. I have to remind myself that we are heading into a situation where "This Firefox" is not the first thing people see but "Setup".
I believe the main reasoning for exposing the USB status as a message was to prevent a situation where users would simply plug in a device and expect something to happen, unaware that USB had to be "switched on" first.
We will soon be exposing that USB switch as soon as people arrive.
In the mockup, I also added the message bar, but in the place that follows the new guidelines, so directly above the section it relates to.
It could be argued that we are doubling up here as the notification that USB is disabled is directly above the new toggle which shows that USB is disabled.
It is perhaps impossible to say which would be most helpful for users at this stage so perhaps the answer is to stick with the sidebar for now and once we have a better idea of what "setup" looks like we can revisit?
So to answer your questions :) ...
Let's keep the behaviour as a message as opposed to a status, we only want to nudge users when their USB debugging expectations might not go to plan, so let's only reveal the message to say "USB disabled".
Really the message only needs to work once for the user to understand that USB isn't necessarily "always on". So I'm thinking.
- The message is present on first visit and remains until either the message is dismissed or the user enables USB.
- If the user dismisses the message and does not enable USB, the message should reamin hidden (they may have no interest in USB debugging).
- If the user enables and then later disables USB, the message should reappear when they return to about:debugging.
- All the time USB is enabled the message remains hidden.
For a title tooltip I agree, it'll be handy to point the user in the direction where they can change the status, so "Enable USB on the Connect page" should suffice. "Dismiss" should be fine for the X button.
Reporter | ||
Comment 12•6 years ago
|
||
As discussed during the standup, we should have enough material here to start the implementation. Closing.
Description
•