W3C home > Mailing lists > Public > www-style@w3.org > August 2015

[css-ui-4] Feedback before f2f

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 24 Aug 2015 12:30:51 +0200
Message-ID: <CAAWBYDCDH_BpngUdAfeqgdDyP+NQpd8d+UXfigba+cx=CBd+PA@mail.gmail.com>
To: www-style list <www-style@w3.org>
Sorry for the generic title, but this feedback crosses across the spec. :/

We (Chrome team) reviewed UI 4 in preparation for the f2f, and have a
few bits of feedback.

1. We should just drop caret-blink-time.  We don't think there's any
actual use-case for controlling this in the first place, and doing so
is an accessibility issue (blinking things too rapidly).  Also, we're
not sure this is actually controllable in OSes.  If you really feel
like screwing with the user, you can do it by flashing caret-color.

2. We should keep 'appearance' limited to just "auto" and "none"
values.  "button" is going to be hard/weird to apply arbitrarily, and
it's not clear the use-case is strong here in the first place.  If you
want something to look like a button, use a <button>.

3. We support changing the name of the "element" value for
'user-select'.  We're happy with the "contain" idea.

4. Can we change the "text" value too?  Maybe to "contents"?  This
value means you can select everything, not just text, so the current
name is weird.

5. We're okay with the text about "user-select:none" and its
application to editting, but are concerned that this isn't the right
spec to talk about this.  Is there an "editting" spec that can talk
about this?  The Editing TF just happened - anything come out of that
we can move this to?

~TJ
Received on Monday, 24 August 2015 10:31:39 UTC

This archive was generated by hypermail 2.3.1 : Monday, 24 August 2015 10:31:40 UTC