<input /> tag that the type is "password" trigger the css transitions in css file that imported by <link /> tag in <head /> tag
Reported by
shann.ch...@gmail.com,
Jun 27 2018
|
|||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Steps to reproduce the problem:
1. An input tag with type attribute "password" exists in the html file.
2.There are transitions properties in the css file for html tag.
3. Refresh browser.
4. The transition of html tag will be triggered.
Supplementary:
The transition css that written in
<head>
<style>
button { transition: all 3s }
</style>
</head>
will not be triggered when refresh browser.
What is the expected behavior?
4. The transition of html tag not be triggered.
What went wrong?
Unusual transition css trigger behavior
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 67.0.3396.99 Channel: stable
OS Version: OS X 10.13.5
Flash Version: Shockwave Flash 30.0 r0
The reduced test case show the different behavior that normal and abnormal.
,
Jun 27 2018
,
Jun 28 2018
,
Jun 28 2018
,
Jun 29 2018
,
Jun 30 2018
Sorry. The 123.zip isn't the file I want to upload. The real test file is below.
,
Jul 2
Able to reproduce this issue on Mac OS 10.13.3, Windows 10 and Ubuntu 14.04 on the latest Stable 67.0.3396.99 as per the original comment. Issue seems to be fixed on the latest Beta 68.0.3440.42 and Canary 69.0.3479.0. Reverse Bisect Information: =========================== Good Build: 68.0.3406.0 (Revision - 553301) Bad Build : 68.0.3405.0 (Revision - 552956) On executing the per-revision bisect script, RuntimeError is coming up. Hence below is the Changelog URL by executing the chromium bisect https://chromium.googlesource.com/chromium/src/+log/7ceb7d256797dfa18b074e062cd982ab2d202b32..ad1435b289845b2faab59c2423071642889871c3 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/1021573 Assigning the issue to Reviewer dvadym@ as vabr@ is not available. dvadym@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks
,
Jul 3
,
Jul 3
Thanks for the report and for the bisect. I have not further investigated whether the linked CL indeed fixed the bug (and what caused it in the first place). However, if we know this is fixed since 68.0.3406.0, then given that 68 is soon becoming stable and we are unlikely to merge anything to 67, I suggest to just close this bug.
,
Jul 18
According to the comment 7, the issue was fixed
,
Nov 29
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by shann.ch...@gmail.com
, Jun 27 2018