dcog989
dcog989
@microsoft-github-policy-service agree
I've done further work on this so closing PR in order to update and resubmit.
> that comment is wrong. Without being part of the spec group, you cannot know why the spec group chose `OKLCh`. But if you want to submit an issue and...
@lhecker - thanks. I'll update this PR tomorrow.
@crutkas, Hi. As per comment in code, alphabetised to aid user selection. We're going from `Oklch` > `OKLCh` (original spec) > `OkLCh` (revised spec incoming) + remove `toupper` so we...
OK, thanks for the review / feedback. I'll investigate - try and build / test locally before offering an update.
@crutkas - I haven't been able to build locally, so cannot test, so abandoning PR.
Another vote for this
I was going to open a ticket for this. I suggest it should be a high priority to address as it is a quite common message to see and very...
@yamadashy - that is the *perfect* solution. Many thanks! :)