Re: [csswg-drafts] [css-align-3][css-anchor-position-1] Do we want to allow `safe` or `unsafe` keywords by themselves / in combination with `normal`? (#12920)

The CSS Working Group just discussed ``[css-align-3][css-anchor-position-1] Do we want to allow `safe` or `unsafe` keywords by themselves / in combination with `normal`?``, and agreed to the following:

* `RESOLVED: Allow 'safe' or 'unsafe' to be combined with 'normal'`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> fantasai: on position-area, when normal alignment is not a simple thing<br>
&lt;ydaniv> ...  does magic stuff<br>
&lt;ydaniv> ... we have a flags about state<br>
&lt;ydaniv> ... so suggestion I have is to allow safe/unsafe to be combined with normal<br>
&lt;ydaniv> astearns: TabAtkins ok with you?<br>
&lt;ydaniv> TabAtkins: strong agree<br>
&lt;ydaniv> astearns: and it would not allow safe by itself?<br>
&lt;ydaniv> fantasai:  [missed]<br>
&lt;fantasai> s/[missed]/we could go either way. Usually we allow default values to be omitted./<br>
&lt;fantasai> align-self: normal<br>
&lt;fantasai> Allow 'align-self: normal &amp;&amp; [ safe | unsafe ]' or 'align-self: normal || [ safe | unsafe]'<br>
&lt;astearns> proposed: allow safe/unsafe to be combined with normal in alignment properties<br>
&lt;ydaniv> PROPOSED RESOLUTION: align-self: normal is combined with safe/unsafe<br>
&lt;ydaniv> astearns: objections?<br>
&lt;fantasai> RESOLVED: Allow 'safe' or 'unsafe' to be combined with 'normal'<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12920#issuecomment-3779709044 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 21 January 2026 17:01:30 UTC