- From: Nick Sherman via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Apr 2020 10:12:27 +0000
- To: public-css-archive@w3.org
> Adding "true physical" units doesn't help here, because there's still no guarantee that the data we get from the OS about the screen's size is physically accurate This is a defeatist attitude toward a chicken and egg situation. Hardware and software makers will have much lower motivation to provide accurate data if there is no standard around which to utilize that data. I agree that it will require time for support to build (perhaps even more time than most features), but that doesn’t mean the idea should just be abandoned. If any new feature was dismissed because it wouldn’t have proper support right away, we would never have any new features. As I mentioned in [an earlier comment](https://github.com/w3c/csswg-drafts/issues/614#issuecomment-254571480): > even if some software environments don't currently access physical display info from the device, that isn’t a reason that none of them ever should. Windows 10 is already providing access to physical measurements for native apps via the [RawDpi property](https://docs.microsoft.com/en-us/uwp/api/Windows.Graphics.Display.DisplayInformation?redirectedfrom=MSDN#Windows_Graphics_Display_DisplayInformation_RawDpiY). Why shouldn’t websites be able to leverage the same info? -- GitHub Notification of comment by nicksherman Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/614#issuecomment-609703615 using your GitHub account
Received on Monday, 6 April 2020 10:12:30 UTC