Closed
Bug 1804146
Opened 2 years ago
Closed 2 years ago
Further clarify why we need NS_CSS_MINMAX
Categories
(Core :: Layout, task)
Core
Layout
Tracking
()
RESOLVED
FIXED
109 Branch
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: TYLin, Assigned: TYLin)
References
Details
Attachments
(1 file)
Bug 763399 has discussed why we want NS_CSS_MINMAX, but I still spend time to figure out the reason independently. It would be good to clarify the document.
|
Assignee | |
Comment 1•2 years ago
|
||
Both std::clamp() and mozilla::clamped cannot handle the case where min >
max.
|
||
Updated•2 years ago
|
Assignee: nobody → aethanyc
Status: NEW → ASSIGNED
Pushed by aethanyc@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/8c989da9c2cd
Clarify why we need NS_CSS_MINMAX. r=emilio DONTBUILD
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox109:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•