On Thu, Jul 19, 2012 at 12:30 PM, Ariel Constenla-Haile <[email protected]> wrote: > On Fri, Jul 20, 2012 at 12:17:37AM +0800, Kevin Grignon wrote: >> KG01 - These examples, along with the behavior expectations may make >> sense to a developer, however in 15 yrs of digital design, I've never >> assumed a tool would resolve my hex input. >> >> I suspect we all agree that the colour picker UX needs work, I'm not >> sure this fix would address the core issues. >> >> Regardless, from a UX perspective, the tool should prevent users from >> having to refine or correct autocomplete. Furthermore, if a specific >> syntax is required, then the input field and supporting instructional >> text and examples should make the expected syntax obvious. > > The problem is: what is the expected behaviour? I didn't get an idea > from the hex numbers I tried, and the documentation is missing/broken > (another issue: F1 doesn't display the respective help page, and AFAIK > the help wasn't updated). >
It depends on what we mean by "expected". I suspect the typical user does not touch hexadecimal. Programmers who are not web developers probably expect this to be treated like a number, i.e., they are entering the three least significant digits and it will be padded with zeros to the left. Some users, those who are web developers, might know (but it is not guaranteed) that CSS3 defines what this means: "The format of an RGB value in hexadecimal notation is a ‘#’ immediately followed by either three or six hexadecimal characters. The three-digit RGB notation (#rgb) is converted into six-digit form (#rrggbb) by replicating digits, not by adding zeros. For example, #fb0 expands to #ffbb00. This ensures that white (#ffffff) can be specified with the short notation (#fff) and removes any dependencies on the color depth of the display." See: http://www.w3.org/TR/css3-color/#rgb-color Regards, -Rob > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina
