New issue
Advanced search Search tips

Issue 648575 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 647694
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

DevRel-SAP: FLexbox behaviour has changed in Chrome 54 Beta

Reported by orit.ha...@sap.com, Sep 20 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Open http://output.jsbin.com/furexucefi.

What is the expected behavior?
Refer to the attached file "Expected result.png"

What went wrong?
Changed behavior for the flexbox rendering.
Refer to the attached file "Wrong behavior.png". 

Did this work before? Yes in Chrome 53

Chrome version: 54.0.2840.27 beta-m  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

Wrong behavior in Chrome 54 Beta and Dev version. It works fine in Chrome 53 and IE11.
 
Expected result.png
14.6 KB View Download
Wrong behavior.png
4.9 KB View Download
Labels: Needs-Bisect
 Issue 648574  has been merged into this issue.

Comment 3 by ajha@chromium.org, Sep 21 2016

Cc: cbiesin...@chromium.org ajha@chromium.org
Components: Blink>Layout>Flexbox
Labels: -Type-Bug -Pri-2 -Needs-Bisect hasbisect-per-revision M-54 ReleaseBlock-Stable OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: jfernan...@igalia.com
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on the latest canary(55.0.2866.0) on Windows-10, Mac OS 10.11.6 and Linux Ubuntu 14.04.

This is regression issue broken in M-54.

Last good build: 54.0.2831.0
First bad build: 54.0.2832.0

Changelog:
==========
https://chromium.googlesource.com/chromium/src/+log/95d9e6b63179642af8391906ccbe586bd3587b56..fe59cb90e7b08f1faa146088ddbd7589d87eebb5

jfernandez@: Could you please take a look at this.

Thank you!
Sure, I'll take a look. I believe this issue is the same than the one reported in  bug #647694 
Mergedinto: 647694
Status: Duplicate (was: Assigned)
Yeah, I confirmed that fix for  bug #647694  also solves this issue.

Sign in to add a comment