You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that for color, the UserModel, minimally requires the values to be valid hex colors only. It will not allow named colors, css rgb(...) specifiers or others. In sheetui I allow both of those currently so would need to either convert them to hex formats before setting the styles or use the lower level model. Is the hex only approach in UserModel intentional?
I would be willing to prepare a PR to add some checking for other valid css values or minimally add documentation to the APi so consumers know what to pass in.
The text was updated successfully, but these errors were encountered:
Hi @zaphar, give me a few days to think about this. So Excel saves them in hex format (I think!). That doesn't mean we have to. I think we definitely should accept named colors,, rbg, etc.
It appears that for color, the UserModel, minimally requires the values to be valid hex colors only. It will not allow named colors, css
rgb(...)
specifiers or others. In sheetui I allow both of those currently so would need to either convert them to hex formats before setting the styles or use the lower level model. Is the hex only approach in UserModel intentional?I would be willing to prepare a PR to add some checking for other valid css values or minimally add documentation to the APi so consumers know what to pass in.
The text was updated successfully, but these errors were encountered: