Bug 169700

Summary:

CSS align-items and justify-content are ignored when flex container is a button element

Product:

WebKit

Reporter:

Phil <pguerrant>

Component:

CSS

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

dvpdiner2, facetothefate, hyatt, jonlee, m.kurz+webkitbugs, oliverjash, simon.fraser, webkit-bug-importer, zalan

Priority:

Keywords:

InRadar

Version:

Safari 10

Hardware:

Unspecified

OS:

Unspecified

Attachments:

Description	Flags
Test Case	none
Test run on safari 11	none
Screenshot of actual output of Safari 8	none

Phil

Reported 2017-03-15 15:22:47 PDT

Created attachment 304560 [details] Test Case See attached test case. The align-items and justify-content properties seems to be completely ignored when the flex container is a button. It doesn't seem to matter if the flex direction is row or column, or what value you use for align-items and justify-content - setting them does not affect any change whatsoever. Works as expected in Chrome, Firefox, IE11, and Edge. Fails only in Safari

Attachments
Test Case (869 bytes, text/html) 2017-03-15 15:22 PDT, Phil	no flags	Details
Test run on safari 11 (166.72 KB, image/png) 2017-09-19 19:22 PDT, Zhifei Fang	no flags	Details
Screenshot of actual output of Safari 8 (14.25 KB, image/png) 2017-12-05 04:06 PST, Oliver Joseph Ash	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2017-03-15 19:24:06 PDT

<rdar://problem/31080695>

Zhifei Fang

Comment 2 2017-09-19 19:18:21 PDT

Looks fine on Safari Version 11.0 (12604.1.38.1.7)

Zhifei Fang

Comment 3 2017-09-19 19:22:40 PDT

Created attachment 321277 [details] Test run on safari 11

Oliver Joseph Ash

Comment 4 2017-12-05 04:06:42 PST

Created attachment 328444 [details] Screenshot of actual output of Safari 8 Note the attached test case image is wrong. It shows the expected output instead of the actual output. I have attached a corrected screenshot of the actual output on Safari 8. This does appear to be fixed in Safari 11.

Jon Lee

Comment 5 2017-12-05 23:54:35 PST

Thanks for the confirmation.

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