From graphical operating systems, people are used to clicking on the words associated with a control (i.e. checkbox, radio button, etc.) and having it activate the control. More and more websites do this too now, and we could too. Where:
- hard/soft form radio buttons
- radio and checkbox Pointer *inputs
it works on the hard/soft form radios now. where else?
Not working for me.
--John Abbe.....Tue Jun 09 04:01:13 -0700 2009
is there a specific todo here?
--Ethan McCutchen.....Thu Dec 01 15:30:16 -0800 2011
Basically not (cool!). Only one place I can think where it could become an issue:
- On the rules interface all of the labels on controls for roles ("Groups") and sets are currently links. Arguably it would be less confusing for Wagneering newbies for clicking on them to activate the control rather than take you to some other page. If that makes sense, we can ticket unlink role and set labels in rules interface.
There are other changes we might make in the future where this would be an issue (e.g. upgrade Toggles to be label-able radio buttons), but we can just try to keep it in mind whenever we're adding new interface with controls where this is relevant.
I just linked those sets in response to improve set choice interface in rule editor. Maybe we should come up with a comprehensive proposal that best meets these conflicting needs (without being too noisy)? Personally I find linking to sets and roles highly valuable and the controls issue in this ticket only marginally so. To my mind, so long as the links open in a new target window (as they do with sets; not sure about roles), then it's not all that disorienting; the original context is not lost.
re toggles, I think the way to go is to get rid of them and handle them as pointers. There really should be one main way to do checkboxes (even booleans).
--Ethan McCutchen.....2013-03-27 16:00:57 +0000
Groups/roles are opening in the same tab/window - ticket make role links in rules open in new target window?
Agree re toggles.
--John Abbe.....2013-03-27 21:20:22 +0000
no need to ticket; that's coded in dev.
--Ethan McCutchen.....2013-03-27 22:00:58 +0000
well, you can if you want to track it...
--Ethan McCutchen.....2013-03-27 22:01:22 +0000
--John Abbe.....2013-03-28 00:21:49 +0000
+discussed in support tickets+relevant user stories