New issue
Advanced search Search tips

Issue 700029 link

Starred by 8 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CSS flexbox: align items not respected by button element

Reported by oliverj...@gmail.com, Mar 9 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.6 Safari/537.36

Steps to reproduce the problem:
1. Apply flex to a button element.
2. Give it a height
3. Alter the align-items property

What is the expected behavior?
Children should respect align-items

What went wrong?
Children remain vertically centered

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 58.0.3029.6  Channel: dev
OS Version: OS X 10.12.3
Flash Version: 

Example: http://jsbin.com/lenupa/1/edit?html,css,output

 
It appears to semi work when you have a child with a larger height: http://jsbin.com/lenupa/4/edit?html,css,output
Components: Blink>Layout>Flexbox
Labels: Needs-Bisect Needs-Triage-M58
Labels: -Needs-Bisect -Needs-Triage-M58 M-59 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Thanks for filing the issue.
Able to reproduce the issue on Windows-7, Mac-10.12.3 & Linux Ubuntu 14.04 using Chrome stable version 57.0.2987.98 and canary 59.0.3036.0 with the steps mentioned in comment#0.

This is Non-regression issue, Observed from M30 #30.0.1549.0 and marking it as Untriaged to get more inputs from Dev team.

Thanks..

Comment 5 by e...@chromium.org, Mar 13 2017

Cc: cbiesin...@chromium.org
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 6 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by e...@chromium.org, Apr 11 2018

Status: Available (was: Untriaged)
This is creating a webcompat issue for Firefox, because Web developers assume the behavior of Chrome is the right one, in at least one opportunity.
https://webcompat.com/issues/20086
or https://github.com/webcompat/web-bugs/issues/20086



Labels: Hotlist-Interop
cbiesinger@, do you have a sense for the effort required to fix this?
I'll have to look into this...

Sign in to add a comment