Closed
Bug 1849440
Opened 2 years ago
Closed 2 years ago
Fix float-to-nscoord conversion in LengthPercentage::Resolve
Categories
(Core :: CSS Parsing and Computation, task)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
118 Branch
Tracking | Status | |
---|---|---|
firefox118 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
Details
Attachments
(1 file)
nscoord LengthPercentage::Resolve(T aPercentageGetter, U aRounder) const {
...
return 0.0f;
This ^ 0.0f
should just be 0
, to match the return type (nscoord which is a typedef for int32_t) and avoid an implicit conversion.
Assignee | ||
Comment 1•2 years ago
|
||
This doesn't change behavior; this just avoids an implicit float-to-nscoord
conversion that we were inadvertently triggering for no reason.
Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/981402028450
Return 0 instead of 0.0f from a nscoord-returning function. r=emilio
Comment 3•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•