Incorrect baseline alignment for 'inline-flex' container, whose only flex item has overflow other than visible and top padding

NEW
Unassigned

Status

()

defect
P4
normal
5 years ago
2 months ago

People

(Reporter: kizmarh, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.12786 YaBrowser/13.12.1599.12786 Safari/537.36

Steps to reproduce:

Note: this is not a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=969874 I guess, at least it not looks as one.

1. Add some blocks with `display: inline-flex`
2. Add inner elements inside of them.
2. Give some of the inner elements `overflow` other than `visible`.
3. Add top padding to this inner element.
4. Use `vertical-align: baseline` for the parent ones.

See this example: http://dabblet.com/gist/8887207, note that in all other browsers this example behaves properly.



Actual results:

Element with `display: inline-flex` and `overflow` other than `visible` on inner element have an incorrect baseline, shifted to the amount of its top padding.



Expected results:

Element with `display: inline-flex` and `overflow` other than `visible` on inner element should have proper baseline.
Status: UNCONFIRMED → NEW
Component: Untriaged → Layout
Ever confirmed: true
OS: Mac OS X → All
Product: Firefox → Core
Hardware: x86 → All
See Also: → 969874
Version: 28 Branch → Trunk
Summary: Incorrect baseline alignment for inline-flex block with nested block having overflow other than visible and top padding → Incorrect baseline alignment for 'inline-flex' container, whose only flex item has overflow other than visible and top padding
Priority: -- → P4

Confirming the reporter's suspicion from comment 0: this is indeed not a duplicate of bug 969874 -- that bug is now fixed in Nightly, but this bug's behavior doesn't seem to have changed.

You need to log in before you can comment on or make changes to this bug.