Setting .enabled: false is a worthy suggestion, but I think that would make the problem slightly worse, not better. Animating from disabled×unchecked to enabled×checked would be even more noticeable — and therefore even more distracting — than from enabled×unchecked to enabled×checked.
Having an “unknown” state would work (the micro equivalent to a “skeleton screen” for a screen as a whole), but it seems a bit excessive. It would be a 1/3 increase in visual design work for checkboxes and radio buttons, and a 50% increase for switches, for something that is not only seldom seen, but also, when it is seen, is seen only for a fraction of a second. So, I still think a better approach would be simply not to show the control at all until its value is known. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276066 Title: Checkbox needs 'unknown' state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1276066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs