Closed
Bug 1501263
Opened 6 years ago
Closed 6 years ago
The flex item sizing property section sometimes says that an item couldn't grow because of sibling while it was actually clamped
Categories
(DevTools :: Inspector, defect, P2)
DevTools
Inspector
Tracking
(firefox65 fixed)
RESOLVED
FIXED
Firefox 65
| Tracking | Status | |
|---|---|---|
| firefox65 | --- | fixed |
People
(Reporter: pbro, Assigned: pbro)
References
Details
Attachments
(1 file)
STR:
- open the following test case URL:
data:text/html,<div style="display:flex;width:500px;border:1px solid;"><span style="flex-grow:1;flex-basis:100px;max-width:50px;">item 1</span><span style="flex-grow:1">item 2</span></div>
- open the inspector
- select the first <span> flex item within the flex container
--> Among other things, the flex item sizing property section says:
> Item could not grow, siblings have likely used the extra space.
This is incorrect, the item could not grow because it was clamped by its max-width.
I think we should just remove this sentence.
|
Assignee | |
Updated•6 years ago
|
Summary: The flex item sizing property section sometimes says that an item was "Set to grow" and "Not set to grow" at the same time → The flex item sizing property section sometimes says that an item couldn't grow because of sibling while it was actually clamped
|
|
Assignee | |
Comment 1•6 years ago
|
||
Pushed by pbrosset@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f2a0505d9f54
Dont say that siblings have used all the space when an item was clamped; r=mtigley
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
You need to log in
before you can comment on or make changes to this bug.
Description
•