KG01 - See comments inline On Jul 20, 2012, at 4:57 PM, Armin Le Grand <[email protected]> wrote:
> [..] >> 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 > > Thanks. I think we should stick to that definition. KG01 - Agreed. The W3 definition and rules should be supported. Perhaps our popup help and documentation should include a reference to the W3 material. > Thus I suggest: > - Allow Field as Input (see comments from Regina) > - Ignore when not three or six valid hexadecimal signs KG01 - From a UX perspective, let's focus on error prevention vs error recovery. > - Apply HelpID > - Adapt Help entries > > I will write a task for it when discussion led to a consensus. > >> Regards, >> >> -Rob >> >> >>> >>> Regards >>> -- >>> Ariel Constenla-Haile >>> La Plata, Argentina > > Sincerely, > Armin > -- > ALG >
