Issue metadata
Sign in to add a comment
|
Transitions misbehave when an input element exists on the page
Reported by
pgrevi...@gmail.com,
Dec 20 2016
|
||||||||||||||||||||||||
Issue description
Chrome Version : 57.0.2957.0
URLs (if applicable) :
https://kreditworks.com/static/bug/bug.html
https://kreditworks.com/static/bug/inline.html
https://kreditworks.com/static/bug/fix.html
Other browsers tested: Firefox, IE, Edge
Firefox: OK
IE: OK
Edge: OK
What steps will reproduce the problem?
(1) Load the first example URL (bug.html)
(2) Notice how the paragraph animates
(3) Load the second example URL (inline.html)
(4) The problem is gone
(5) Load the third example URL (fix.html)
(6) The problem is gone
What is the expected result?
In bug.html, the last paragraph should be roughly 250px below the previous paragraph, fully red, and bolded on page load. It should not animate between the initial state and the end state.
What happens instead?
The last paragraph in bug.html animates between its pre-CSS and post-CSS styles over 2 seconds. The background fades in, the text becomes bold about halfway through, and its margin is animated. This does not happen in inline.html mysteriously, and does not happen when there is no input element on the page (fix.html) even more mysteriously.
Additional information:
Screenshots were taken roughly half a second after the page loaded.
,
Dec 30 2016
Able to reproduce this issue on windows 7, Mac 10.12.2,Linux Ubuntu 14.04 with Chrome stable version-55.0.2883.87 and Canary-57.0.2966.0 Manual Bisect: ----------------- Bad Build—47.0.2526.80 Good Build—46.0.2490.86 Since Bisect range is in between branch builds, providing manual bisect using Omahaproxy. Change log from omahaproxy: ----------------------------- https://chromium.googlesource.com/chromium/src/+log/46.0.2490.0..47.0.2526.0?pretty=fuller&n=10000 Review URL: ---------- https://codereview.chromium.org/1308073007 Unable to find the exact suspect from the above CL . timloh@ assigning to you, as you were listed as one of the reviewers for this CL. Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change. Thanks.!
,
Jan 4 2017
Alan - you also reviewed the above CL, do you know what might be going on?
,
Jan 4 2017
I'm not 100% convinced that CL is responsible, the regression range is quite enormous. I would recommend narrowing the regression range as the next step of investigation.
,
Jan 4 2017
,
Jan 9 2017
,
Jan 11 2017
I've run a bisect and narrowed the range to: https://chromium.googlesource.com/chromium/src/+log/134874970be5a25bc7211349faba812a52c3feda..b9d14401ecbc0641a27c24fbe987a7803e258f8f This contains two WebKit rolls: https://chromium.googlesource.com/chromium/blink/+log/04b637a..8122aac https://chromium.googlesource.com/chromium/blink/+log/dd80f89..04b637a which each have one revision each: https://chromium.googlesource.com/chromium/blink/+/8122aacd19b0441c443e821e4f257ace572fbfd6 https://chromium.googlesource.com/chromium/blink/+/04b637abf965f50049cb1c6fbf52cc0c8e925a6a cbiesinger: can you take a look? These changes are outside the animations code, so moving this back to Blink>CSS, but I'll remain cc'd in case you need input from the animations team.
,
Feb 13 2017
,
Feb 13 2017
,
Apr 5 2017
I'm sorry if this bumps the thread! I closed down my website where I was hosting the example files, so they are now attached to this comment.
,
Apr 6 2017
No apology necessary, thanks for uploading the repro files!
,
Apr 13 2017
Related/duplicate - Issue 693088 Issue 709718
,
Apr 14 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 21 2016