4 ms·
And they still managed to get the round corners wrong, apparently. According to that page, the radius values are hardcoded in pixels, so they don't scale with t
by 4cao 5y ago
And they still managed to get the round corners wrong, apparently. According to that page, the radius values are hardcoded in pixels, so they don't scale with the display's DPI setting.
That's at least a decade after the W3C had a well-developed concept of relative units for use with the CSS:
https://www.w3.org/Style/Examples/007/units.html#future https://www.w3.org/Style/Examples/007/units.html#future (2010)
Thus, with a sufficiently high DPI display, you're going to miss out on one of Windows 11's "signature experiences" and end up with "legacy" squarish corners instead.
- 323 5y agoThey use "effective pixels", just like CSS pixels are not actual pixels: > Because of how the scaling system works, when you design your UWP app, you're designing in effective pixels, not actual physical pixels. Effective pixels (epx) are a virtual unit of measurement, and they're used to express layout dimensions and spacing, independent of screen density. (In our guidelines, epx, ep, and px are used interchangeably.) https://docs.microsoft.com/en-us/windows/apps/design/layout/screen-sizes-and-breakpoints-for-responsive-design https://docs.microsoft.com/en-us/windows/apps/design/layout/... Also, Windows scales the pixel size when you use a legacy application (non DPI aware) on high DPI displays.