The problem with the sequence of the result of the code execution.
Reported by
karpu...@gmail.com,
Mar 13 2018
|
||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Steps to reproduce the problem:
1. create: <div id="clickMe">ClickMe!</div>
2. add Event Listener: document.getElementById("clickMe").addEventListener("click", function( event ) {
console.log(event.target.style.color = 'red');
alert("First!");
}, false);
3. Click div with id clickMe
What is the expected behavior?
1. first saw the result of execution event.target.style.color
2. after saw alert
What went wrong?
1. after saw alert
2. first saw the result of execution event.target.style.color
Did this work before? N/A
Chrome version: 64.0.3282.186 Channel: n/a
OS Version: 10.0
Flash Version:
Firefox works with it correctly.
It's probably the result of the result renderer in the DOM.
Console.log works correctly.
,
Mar 23 2018
,
Mar 29 2018
Unable to reproduce the issue on Windows 7 & Mac 10.13.3 using chrome reported version-64.0.3282.186 & latest stable-65.0.3325.181 as per C#0. Please find the attached screencast for reference & if possible provide us the sample html file to triage this issue from our end. Thanks..!
,
May 22 2018
As per comment #3 unable to reproduce the issue and marking it as WontFix since there are no feedback from user more than a month.Feel free to raise a new issue if still facing. Thank You!
,
Jun 14 2018
Please look here: https://jsfiddle.net/kauz2hpn/2/ Explanation: It is necessary to look at the color of the text of the element, and not the output in the console. ------- But I think I know why this is explained. First the code is executed, then the rendering takes place. While in another browser (like Firefox) the order of execution is expected.
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 13 2018