[indicators] Clicking on a connected network's disconnects & re-connects

Bug #1322490 reported by Dave Morley on 2014-05-23
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu UX
Medium
Matthew Paul Thomas
indicator-network (Ubuntu)
Medium
Antti Kaijanmäki
ubuntu-settings-components (Ubuntu)
Medium
Unassigned
unity8 (Ubuntu)
Undecided
Unassigned

Bug Description

indicator-network 0.5.1+14.10.20140516.2-0ubuntu1, Ubuntu Utopic

1. Unlock the phone
2. Drag down the indicator for networking
3. Select a wifi AP sign into it
4. Drag down the indicator for networking
5. Try to uncheck it.

What happens: The network disconnects and reconnects.

What should happen: Nothing.

<https://wiki.ubuntu.com/Networking#wi-fi-menu>: "2. If the card is powered on, up to 6 (phone) or 20 (PC) radio items representing known Wi-Fi networks..."

Dave Morley (davmor2) wrote :
tags: added: flo mako manta u44
Changed in indicator-network (Ubuntu):
importance: Undecided → High
Dave Morley (davmor2) on 2014-05-23
Changed in indicator-network (Ubuntu):
assignee: nobody → Antti Kaijanmäki (kaijanmaki)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-network (Ubuntu):
status: New → Confirmed
Antti Kaijanmäki (kaijanmaki) wrote :

Right now it is intended behaviour that you can't disconnect by tapping an active AP in the list. Instead that will trigger a reconnection. If you don't want to connect to that AP either disable Wi-Fi or select another AP to connect to.

We will discuss this behaviour at Malta next week.

Changed in indicator-network (Ubuntu):
status: Confirmed → Opinion
Matthew Paul Thomas (mpt) wrote :

As I wrote in duplicate bug 1322497, the list of networks is a radio list. In a radio list, re-selecting the current item should not change state; it should rarely do anything at all. (Bug 1322321 is a counterexample that demonstrates the rule; it's okay for re-selecting a sound to play the sound, because that isn't changing state.)

That both Dave and Selene assumed that these were uncheckable checkboxes suggests that either the menu is using checkboxes when it should be using a radio list, or the toolkit is wrong in presenting radio lists as if they were checkboxes.

Meanwhile, though, this bug is valid in that re-selecting the current network should not trigger a reconnection.

(Please don't use the "Opinion" status for bug reports; everyone thinks it means something different.)

Changed in indicator-network (Ubuntu):
status: Opinion → Confirmed
Matthew Paul Thomas (mpt) wrote :

Specification updated. <https://wiki.ubuntu.com/Networking?action=diff&rev2=189&rev1=188> Please report the toolkit bug separately if there is one.

Changed in indicator-network (Ubuntu):
status: Confirmed → Triaged
description: updated
Selene ToyKeeper (toykeeper) wrote :

Yes, if it's a radio list, it should not be displayed with a checkbox icon. Checkboxes can be un-checked. A radio selection icon would make this much more clear.

It might be nice to be able to disconnect without turning off wireless entirely, but I don't see this being a very common need. If it's easy to do, I see no reason not to... but if it's not easy it probably doesn't need to happen.

Tony Espy (awe) wrote :

Confirming that this is still a valid issue with image #u122.

Tony Espy (awe) on 2014-07-09
summary: - Clicking on the checkbox to disconnect from an ap sometimes disconnects
- but always leaves the box checked
+ Clicking on a connected network's checkbox disconnects & re-connects
tags: added: rtm14 touch-2014-10-09
Joe Odukoya (jodukoya) wrote :

Ubuntu UX needs to decide what the actual behaviour should be here.

However this is not a High bug.

Changed in indicator-network (Ubuntu):
importance: High → Medium
Antti Kaijanmäki (kaijanmaki) wrote :

AFAIK the correct fix is to make the list look like list selection and not checkboxes. that was the last resolution on this if I remember correctly. then it would be on unity8 / ubuntu-settings-components plate.

Matthew Paul Thomas (mpt) wrote :

Joe, the relevant part of the design specification has been quoted in the bug description since May 28th: "up to 6 (phone) or 20 (PC) radio items representing known Wi-Fi networks". Radio items. Not checkbox items. Radio items.

no longer affects: ubuntu-ux
summary: - Clicking on a connected network's checkbox disconnects & re-connects
+ [indicators] Clicking on a connected network's checkbox disconnects &
+ re-connects
Changed in ubuntu-ux:
assignee: nobody → Vesa Rautiainen (vesar)
Changed in ubuntu-ux:
status: New → Triaged
importance: Undecided → Medium

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-settings-components (Ubuntu):
status: New → Confirmed
Changed in ubuntu-settings-components (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Pete Woods (pete-woods) on 2015-03-26
no longer affects: indicator-network
Vesa Rautiainen (vesar) on 2015-05-08
Changed in ubuntu-ux:
assignee: Vesa Rautiainen (vesar) → Matthew Paul Thomas (mpt)
Antti Kaijanmäki (kaijanmaki) wrote :

This bug is invalid on i-network side. unity8 rendering the lists items should not tricker an "Activated" signal on an already activated AccessPoint

Changed in indicator-network (Ubuntu):
status: Triaged → Invalid
Antti Kaijanmäki (kaijanmaki) wrote :

adding unity8 to the affected packages as it might be easier (probably a oneliner) to fix this in the unity8 IndicatorItemFactory.

summary: - [indicators] Clicking on a connected network's checkbox disconnects &
- re-connects
+ [indicators] Clicking on a connected network's disconnects & re-connects
Albert Astals Cid (aacid) wrote :

I'm unsure of what you mean Antti, you mean we're rendering a checklist even if the backend is not sending a checlist but an itemlist?

Albert Astals Cid (aacid) wrote :

unity8 waiting for design -> Incomplete

Changed in unity8 (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers