> Text fields used to, as Christian says,
> change background color distinct from their focus ring.
> It’s good that they no longer do,
> because it made unfocused fields look disabled.
> So now they should have a focus ring instead
Text fields show a caret whenever they accept keyboard (or OSK) input -
they do show a focus ring only when focused via keyboard.
> A. Give the switch a focus ring
Focus ring on tap would mean changing what focus ring means.
> B. So, make the selected list item look selected then [...]
Selected item? Maybe. How about selected switch?
> C. Make tapping not select the list item [...]
Keyboard focus should follow tap/ click so that pressing (Shift)Tab moves
relative to the component last interacted with - that's a requirement right now.
Conceivably the behavior could be changed to 'anything that won't visually show
keyboard input takes no focus on tap' provided all components including other
types of buttons are re-visited and the keyboard navigation requirement above
is re-visited.
This goes back to my point, we have no requirement to show that input is
accepted, except for text input as a special-case.
** Changed in: ubuntu-ux
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549733
Title:
SystemSettings Language&Text view: hitting Space on HW keyboard
triggers switch even when it (or its list item) does not show any
visual focus frame
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549733/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
