-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Units of properties are not pixels, they are density-independent pixels #926
Comments
I'm not 100% sure, but I see all kind of scaling in the code related to device pixel ratio. |
We could use 'dp' instead of 'device-independent pixel'. https://en.wikipedia.org/wiki/Device-independent_pixel |
I'm not sure dp is intuitive to everyone as opposed to pixels. |
Yeah, there are lots of places around the code where The correct term is |
I think that might actually be more confusing. Also, it's a spec, we should use the correct term in my opinion. We could link each mention of dp to an explanation. Or write (device-independent) pixels. |
Unsure if y'all are using Material for Mkdocs, but if so, the Abbreviations feature seems perfect for this use case: https://squidfunk.github.io/mkdocs-material/reference/tooltips/#adding-abbreviations DP (or dips) is probably the correct generic term, and the tooltip can clarify that's the same as a CSS px on web |
Thanks for the tip, we are using mkdocs material for the docs. |
Some properties, like
circle-radius
list the unit as pixels:In the case of native, they are actually density-independent pixels. So the amount of pixels depends on the pixel ratio (also called pixel density). I think this is also true for MapLibre GL JS? (cc @ibesora)
The text was updated successfully, but these errors were encountered: