- From: Kevin Muldoon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2023 10:03:37 +0000
- To: public-design-tokens-log@w3.org
A traditional px (or point) is the appropriate value, where REM/EM are derived values that are driven by the idea of a CSS Pixel. I believed 1pt was always equal to 1px (1/72") because iOS specifies typography in points, and that is how print works. I am confirmed in my belief when I set spec typography as size 17 (in Sketch, Figma, or Illustrator) as a developer handoff, I can screenshot the render of that design on my iOS device and expect it to overlay perfectly on my designs. Even though Illustrator says the typography is in points and documentation in Figma says it's in px, both line up perfectly. The problem occurs only on the web, with the idea of a CSS Pixel. This strange concept gives us math such as... `17pt == 22.66px == 1.4167rem ` This ASSUMES a root font-size of 16px, and as we know, that is a variable that could be changed to anything in the web dev environment. Therefore, we should consider using the unit specification that matches the input defined by the designer in a design application as 'the standard', and leave the job to programmers to transform to any platform-specific values they like via Style Dictionary transforms.. -- GitHub Notification of comment by caoimghgin Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/218#issuecomment-1552826394 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 May 2023 10:03:40 UTC