[docs][system] Update sizing docs to clarify (0, 1] behavior.#47845
Merged
ZeeshanTamboli merged 1 commit intomui:masterfrom Feb 24, 2026
Merged
[docs][system] Update sizing docs to clarify (0, 1] behavior.#47845ZeeshanTamboli merged 1 commit intomui:masterfrom
(0, 1] behavior.#47845ZeeshanTamboli merged 1 commit intomui:masterfrom
Conversation
Signed-off-by: Matthias <18034092+matthias-ccri@users.noreply.github.com>
Netlify deploy previewBundle size report
|
ZeeshanTamboli
changed the title
(0, 1] behavior.(0, 1] behavior.
ZeeshanTamboli
added
scope: system
|
Cherry-pick PRs will be created targeting branches: v7.x |
github-actions bot
pushed a commit
that referenced
this pull request
Feb 24, 2026
Signed-off-by: Matthias <18034092+matthias-ccri@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding some qualifiers to the docs that said "[All] numbers are treated as pixel values" -- that's simply not the case. For library authors animating values or supporting continuous values that may go into the range of 0..1 -- they may encounter surprises if they take at face value the statement "numbers are pixels" (if only that were true!) 😄
RE the phrasing change ("converted to" versus "treated as") -- no conversion is taking place. Conversion happens when converting a number from one unit into another. It requires a "from" unit and a "to" unit. It appears that "pixels" is the "from" unit. And pixels is also the "to" unit because the style output is a pixel string like
${n}px. One does not say "convert a pixel to a pixel".The phrasing of "treated as" makes sense. The library treats these numbers as if they were pixel values. Hence the phrase "treated as numbers".