After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793238 - Misleading wi-fi refresh button
Misleading wi-fi refresh button
Product: gnome-control-center
Classification: Core
Component: Network
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Reported: 2018-02-07 08:57 UTC by Allan Day
Modified: 2018-02-20 09:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Allan Day 2018-02-07 08:57:35 UTC
A new refresh button was added to the wi-fi panel, as part of bug 789869.

Since it is permanently visible, and there's no feedback when scanning is taking place, it leads the user to think that they have to click it whenever they want to scan. This isn't good in terms of helping the user, and leads to a kind of intensive micro-management interaction that we generally try to avoid in GNOME.

In my testing, pressing the the button had no visible effect - it stayed raised and there was no indication that scanning was taking place

You could provide feedback when scanning is taking place, but then you end up in a whack a mole situation, with the user constantly having to monitor the state of the panel in order to hit the button when scanning stops.

From the original bug, it isn't entirely clear why the button is needed. I wish there had been some design review before the change was landed.
Comment 1 Felipe Borges 2018-02-19 09:24:29 UTC
UI Freeze break request
Comment 2 Felipe Borges 2018-02-20 09:09:30 UTC
As we discussed on IRC, I have reverted the changes in commit 849e50b after given the two ACKs from the release team to break the UI freeze break.

In another issue (in gitlab) we could discuss and propose alternatives for triggering the scanning.
Comment 3 Allan Day 2018-02-20 09:53:30 UTC
Thanks Felipe - much appreciated.