Open
Bug 1512313
Opened 5 years ago
Updated 2 years ago
[remote-dbg-next] Refresh devices status & action in sidebar
Categories
(DevTools :: about:debugging, enhancement, P3)
DevTools
about:debugging
Tracking
(Not tracked)
NEW
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
The Refresh Devices button is a workaround because we sometimes don't get updates about devices connections disconnections from ADB. However it's not clear for the user when they should use this button or not. Instead we could simply automatically refresh the list periodically.
Reporter | ||
Comment 1•5 years ago
|
||
ni: summarize current discussion about our options here
Flags: needinfo?(jdescottes)
Priority: -- → P2
Summary: [remote-dbg-next] Automatically update devices list instead of having a "refresh devices" button → [remote-dbg-next] UX: Refresh devices status & action in sidebar
Reporter | ||
Comment 2•5 years ago
|
||
(trying to summarize the conversations about this topic on Slack with Belén, Matt and Ola) The refresh button currently often needs to be used, because we don't get updates related to the Firefox runtime starting/stopping on a remote device. We would like to replace this "runtime update" by a rather frequent polling (every few seconds). We are also thinking about showing to users that this scan is happening with a small animation. This could also be combined with an action button to trigger the refresh manually. The animation should be very subtle, and we should offer a static alternative for users who opted for the `prefer-reduced-motion` setting. However if we are talking about something that happens every few seconds (few < 10), then the animation will be too frequent, and clicking on the button will not make much sense. We can introduce two different types of "refresh". A very frequent one for "runtimes" and a more complete one that would refresh both "devices" and "runtimes". The action button and user feedback would only be associated with this second type of refresh.
Flags: needinfo?(jdescottes)
Reporter | ||
Comment 3•5 years ago
|
||
We landed some small polling for runtime updates in Bug 1508956. Here are some items that were brought up during the review and that should be finalized when we tackle this bug: - should we do auto polling for all consumers of adb.js (more technical than UX :) )? - should we ask to user whether user wants polling? - are there places where we do polling like this in devtools or somewhere?
Comment 4•5 years ago
|
||
> should we ask to user whether user wants polling?
What are the trade offs when we always poll (when it is useful, like the page being in foreground)?
Reporter | ||
Comment 5•5 years ago
|
||
Removing UX tag, moving to reserve.
Priority: P2 → P3
Summary: [remote-dbg-next] UX: Refresh devices status & action in sidebar → [remote-dbg-next] Refresh devices status & action in sidebar
While reviewing https://phabricator.services.mozilla.com/D24419 an idea came up for the styling of the button.
Proposal:
Extending the width of the Refresh devices
button on the right side to match the end of the connect button.
I feel like as the USB enabled
kind of works as a header, extending the width of the button could help with grouping the devices and their actions thought aligning it to the given grid.
(width aligned to connect button)
https://bug1512313.bmoattachments.org/attachment.cgi?id=9052813
(without notification)
https://bug1512313.bmoattachments.org/attachment.cgi?id=9052814
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•