It's very easy to pass in a DIP point to a function that needs physical points. The terminology used in scaling also collides with coordinate systems (e.g. a point in the screen coordinate system (origin reference) or a point using screen dimensional measurement (actual physical pixel size).

First we should agree on the terminology to use for actual pixels on the screen (e.g. Native, Physical) and for virtualized pixels (e.g. DIP, Logical).

With this naming scheme, clean up Chromium to be consistent with the naming and introduce types that make it difficult to accidentally pass in a DIP point to a function that expects physical points (e.g. NativePoint or PhysicalPoint and DIPPoint or LogicalPoint).