[policy, no patch] Are CSS changes change record worthy?

Let's see if we can resolve this.

I've asked in #core-development and #css for some feedback.

jacine replied in #frontend giving examples where the change record is needed for CSS changes. And there are change records for CSS changes, so this is happening. The policy is deliberately general to allow flexibility but we could add a phrase to include CSS.

As mentioned in slack.

If the css change is in claro or olivero I’d be less inclined to say a CR is needed.

But if the change is on the module level then I think to be safe a CR should be included.

Extreme example but what if field_item class gets background red added to it. It would be nice to announce such a change

Thoughts?

I changed the policy the make it clear that CSS changes are to be considered. I did not attempt to define what a significant CSS change would be or to provide examples. I think it is OK to be flexible and allow those working on a issue to decide.

I am going to close this. The change is only a few words and simple.

Thanks

Automatically closed - issue fixed for 2 weeks with no activity.

Changing to latest version when this was closed.