- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Mar 2021 14:34:47 +0000
- To: public-css-archive@w3.org
Any design flaw can and has been addressed via documentation/education, but that's usually a bandaid when it's too late to change the design. It's one of the basic antipatterns usability to avoid designing UIs that require documentation/education to make sense, since most people will *not* read much documentation, and you can never reach everyone to educate. UIs (including APIs) need to be designed to be understandable and usable even in the absence of documentation/education. The more I think about this, the more I think that the most reasonable thing is for percentages out of range to *extrapolate* along the same line. Even if there are no use cases, it provides useful **feedback** which aids debugging, and is no harder to implement than regular interpolation (if anything, *not* doing this is probably extra implementation work). Note that there is precedent of extrapolation in CSS, with transitions with certain timing functions that make the interpolated value go beyond 100% ([demo](https://dabblet.com/gist/4d08254b01a167c242f24949d4f61fc2)). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6047#issuecomment-790661627 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 March 2021 14:34:49 UTC