Are you willing to submit a PR to fix? (Possibly?)
Requested priority: Normal
In the <ColorPicker>
component there are Textarea
s beneath the palette and sliders which show the hex, R, G, B and A values.
These Textareas are not read-only, so one would expect that changing the values manually here would be reflected in the state of the ColorPicker (e.g. pasting a known hex value would make the picker jump to the appropriate point in the swatch.
Changing text values in the color picker does not alter the color as expected.
Selector point in the swatch should jump to the appropriate color.
Many thanks!
Thanks for explaining the issue in details but I would still want to keep the hex text area editable. There are users that uses that and change is reflected in color palette. For RGB and A, we should make them read- only if no users are using them.
@mdahamiwal is that really the case?
http://dev.office.com/fabric#/components/colorpicker I change the hex values here and the colour doesn't change at all. See screenshot:
There seems to be no reason to have these values editable if editing them does nothing.
That's right, I misunderstood the visible (hex) with the prop change (color) that we handle gracefully. I am okay with having all the text inputs as uneditable or render labels instead of text boxes to improve accessibility.
@mikewheaton, thoughts ?
I have a PR out, the entire control should now update to the correct values when any other part of the control changes, which means changing a text field value will update the swatch and sliders.
Most helpful comment
I have a PR out, the entire control should now update to the correct values when any other part of the control changes, which means changing a text field value will update the swatch and sliders.