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
Given that CSS Color 4 is not yet a Candidate Recommendation, it still seems worthwhile to republish an updated Rec of CSS Color 3. And recent Process changes mean that we just republish; there is no going back to CR or PR here.
The same edit as was made to CSS Color 4, replacing the error-strewn HSL table which had allegedly been generated by ABC, with a correct version. The ABC conversion code is also swapped for the same JS code used in CSS Color 4 Issue 3088
Clarified case-insensitive is ASCII case-insensitive Issue 4599
Note that it is no-longer realistically possible to use the old .src files as input. Bitrot, and vastly changed pubrules requirements means that the conversion requires a lot of hand-editing of the generated output. Instead, to ensure that the diff from the published, 19 June 2018 Recommendation is small, I have been directly editing the generated file. This is fine for small maintenance changes (same issue for CSS Fonts 3 actually].
Agenda+ for a resolution to publish
The text was updated successfully, but these errors were encountered:
The CSS Working Group just discussed [css-color-3] Publish updated Recommendation with Candidate Corrections, and agreed to the following:
RESOLVED: Publish Colors 3 as updated Recommendation with Candidate Corrections
The full IRC log of that discussion
<dael> Topic: [css-color-3] Publish updated Recommendation with Candidate Corrections
<dael> github: https://github.com//issues/6486
<dael> chris: Long bug with hsl colors. Color 3 has ABC program for that. Report that almost 50% of values are wrong.
<dael> chris: Fixed in color 4 by running the JS. Having done that made sense to put in L3.
<dael> chris: Also a couple of little changes in ED that I also did as candidate corrections. We can pub and get that moving. Doesn't require directors decision, just decision to publish
<dael> astearns: Concerns?
<dael> florian: Question- we're positive JS ir right?
<dael> chris: Yes
<dael> florian: Rest is editorial?
<dael> chris: Yes
<dael> chris: Removed media from propdef is in as candidate
<dael> florian: Sure. process def of editorial is narrow
<dael> chris: They're prop corrections that allow you to see in place the change. Proposed corrections have normative force
<dael> florian: If parts of spec are editorial you can do them immediately. if they grey
<dael> chris: I think it's grey zone
<dael> astearns: Other comments?
<dael> astearns: Obj to Publish Colors 3 as updated Recommendation with Candidate Corrections
<dael> RESOLVED: Publish Colors 3 as updated Recommendation with Candidate Corrections
<dael> astearns: Other publishing things?
Given that CSS Color 4 is not yet a Candidate Recommendation, it still seems worthwhile to republish an updated Rec of CSS Color 3. And recent Process changes mean that we just republish; there is no going back to CR or PR here.
Accordingly I have prepared an updated draft of CSS Color 3. It includes three Candidate Corrections.:
Note that it is no-longer realistically possible to use the old .src files as input. Bitrot, and vastly changed pubrules requirements means that the conversion requires a lot of hand-editing of the generated output. Instead, to ensure that the diff from the published, 19 June 2018 Recommendation is small, I have been directly editing the generated file. This is fine for small maintenance changes (same issue for CSS Fonts 3 actually].
Agenda+ for a resolution to publish
The text was updated successfully, but these errors were encountered: