Closed
Bug 1380602
Opened 7 years ago
Closed 5 years ago
Vertical margin and padding in percent in the inner of flex layout container
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 958714
People
(Reporter: kyvenko.sergiy, Unassigned)
Details
(Keywords: stale-bug)
Attachments
(1 file)
68.56 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce: 1. create flex container 2. create inner element 3. add some vertical margin or padding (if inner elem have not display:table) in percent p.s. if parent flex container has fixed height then vertical margin or padding is work Actual results: In the inner element padding or margin, is equal 0 Expected results: vertical padding or margin should have some value, not 0
Reporter | ||
Updated•7 years ago
|
Severity: normal → critical
Priority: -- → P1
Updated•7 years ago
|
Component: Untriaged → Layout
Product: Firefox → Core
Reporter | ||
Updated•7 years ago
|
OS: Unspecified → All
Hardware: Unspecified → All
This is a P1 bug without an assignee. P1 are bugs which are being worked on for the current release cycle/iteration/sprint. If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Comment 2•7 years ago
|
||
Please don't set the Priority field unless you're part of the team who works on these bugs. This is definitely not a P1. Definitely an annoying bug, but more like P4 as per https://dbaron.org/log/20090120-bug-priorities
Severity: critical → normal
Priority: P1 → --
Comment 3•7 years ago
|
||
Can you attach a testcase that demonstrates the issue that is as simple as possible, please?
Flags: needinfo?(kyvenko.sergiy)
Reporter | ||
Comment 4•7 years ago
|
||
https://codepen.io/Dezmonds/pen/YrqOwm I added bug preview on this link, on Mozilla vertical margin in percent is null
Flags: needinfo?(kyvenko.sergiy)
Updated•7 years ago
|
Comment 5•5 years ago
|
||
It looks like the codepen is now 404. I'm guessing this was a duplicate of bug 958714 based on the description, though.
So: should be fixed now, but please reopen if this is still an issue (and if you could resurrect a testcase in that scenario, that'd help too). Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•