Issue metadata
Sign in to add a comment
|
Buttons and Textfields not displayed properly after Google Chrome updated to 55.0.2883.95 (64-bit)
Reported by
diego.de...@robosoftin.com,
Dec 20 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Launch the app provided in the attachment below on a server in google chrome version 55.0.2883.95 (64-bit) . 2. Enter the project name and observe the designer. 3. Click on 'Start Designing' Button and observe the designer. What is the expected behavior? 1. On entering project name, the place holder should be hidden. 2. On clicking 'Start Designing' Button new window is displayed with textfields, buttons, radio buttons and popup button. What went wrong? 1. On entering project name, placeholder overlaps on entered text. 2. On clicking 'Start Designing' Button new window is displayed with missing radio buttons, popup button and missing some textfields. Did this work before? Yes 54.0.2840 Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.9.5 Flash Version: Shockwave Flash 24.0 r0 Attached project is developed using Cappuccino Framework 0.9.1. The attached app properly displayed in previous version of google chrome as well as beta version 56.0.2924.28.
,
Dec 22 2016
I haven't been able to setup the repro so I can't confirm. This seems like a paint invalidation issue though since the controls appear when hovered.
,
Dec 22 2016
,
Dec 23 2016
Updated "SampleApplication" attached below, since the problem caused was regarding import issue. Please use a localhost server (For ex. python -m SimpleHTTPServer) to run the app.
,
Dec 23 2016
Reproduced using #5 on Windows + Chrome x64 so it's not Mac-specific. Couldn't reproduce in Chrome x86 though. Broken in 54.0.2839.0: 414097 (good) - 414103 (bad) https://chromium.googlesource.com/chromium/src/+log/c0ec8559..36e71623?pretty=fuller Fixed in 56.0.2906.0: 428693 (bad) - 428695 (good) https://chromium.googlesource.com/chromium/src/+log/1b37cd6a..ddfbff15?pretty=fuller These changelogs don't make much sense to me because the only common change is V8 update and I can't imagine it being the cause but who knows maybe this will be useful for the dev team...
,
Dec 23 2016
Thanks for the investigation! Ok, I managed to reproduce on Windows as well (though not on Linux). Interesting that you found a difference between 64 and 32 bit, but that'd explain why Linux works (we only ship 32 bit Linux binary). The bug appears fixed for me in Canary (and 56 (beta) as your bisect noted). The application is rather complex so it's hard to tell what's actually going on but it does look like there's heavy use of JS to put everything together. The fixing CL your bisect pinpointed is a rather large change. Combined with the 64/32 difference it does seem like V8 had something to do with it. Anyway, given that 55 is already well into shipping and this is fixed in 56, I don't think there's anything more to do but wait until the fix ships. I'm going to close this but feel free to reopen if you still see it in 56 onward. Thanks for the help. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tkent@chromium.org
, Dec 20 2016