Re: [csswg-drafts] [css-backgrounds] Specify exact pixel values for border-width: thin, medium, thick (#7254)

The CSS Working Group just discussed `[css-backgrounds] Specify exact pixel values for border-width: thin, medium, thick`, and agreed to the following:

* `RESOLVED: thin, medium, and thick will be defined as 1px, 3px, and 5px respectively.`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-backgrounds] Specify exact pixel values for border-width: thin, medium, thick<br>
&lt;emeyer> Github: https://github.com/w3c/csswg-drafts/issues/7254<br>
&lt;emeyer> TabAtkins: Was noticed that we still leave the keyword thicknesses undefined.  But all browsers agree on widths at 1px, 3px, 5px.<br>
&lt;emeyer> …Not sure of the exact history, but absent that, the widths are very consistent and don’t see a good reason to leave them undefined.<br>
&lt;astearns> ack fantasai<br>
&lt;emeyer> fantasai: Maybe it was that these were like font-size keywords and left open to interpretation.  We should maybe recommend but not require specific widths.<br>
&lt;fantasai> My suggested wording was “For Web compatibility, it is recommended that these keywords be mapped to 1px, 3px, and 5px, respectively.”<br>
&lt;emeyer> TabAtkins: On the other hand, we specify a lot of things that could be adjusted by e-readers.  I don’t know that this needs to be left undefined.<br>
&lt;emeyer> …I argue we should go stronger than suggested.<br>
&lt;astearns> ack dbaron<br>
&lt;emeyer> dbaron: This is one of those things that was left up in the air in CSS1, and I don’t remember a proposal to define more precisely.  I support the precise definition.<br>
&lt;emeyer> fantasai: If everyone else agrees, that’s fine.<br>
&lt;emeyer> RESOLVED: thin, medium, and thick will be defined as 1px, 3px, and 5px respectively.<br>
</details>


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


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

Received on Wednesday, 11 May 2022 16:09:48 UTC