Create two inputs.
Reported by
gerardor...@gmail.com,
Jan 10 2018
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Steps to reproduce the problem:
Note: Create a console.log("Test Focus In" + element.getAttribute("name")) and console.log("Test Blur" + element.getAttribute("name")) in focusin and blur event for each input.
1. Click one element
2. Click the second element
3. Click the first element
4. Click outside chrome
5. Click the second element inside chrome.
What is the expected behavior?
LOG:
Test Focus In FirstElement
Test Blur FirstElement
Test Focus In SecondElement
Test Blur SecondElement
Test Focus In FirstElement
Test Blur FirstElement
Test Focus In SecondElement
What went wrong?
BUT THIS HAPPEN
LOG:
Test Focus In FirstElement
Test Blur FirstElement
Test Focus In SecondElement
Test Blur SecondElement
Test Focus In FirstElement
Test Blur FirstElement
--Test Focus In FirstElement *When entering the windows immediately trigger Focusin and blur for the last element before leaving the window.
--Test Blur FirstElement
Test Focus In SecondElement
Did this work before? N/A
Chrome version: 63.0.3239.132 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
,
Jan 11 2018
Issue 800869 has been merged into this issue.
,
Jan 11 2018
,
Jan 11 2018
Thanks for filing the issue! @Reporter: Could you please share a sample test file/URL which helps us in triaging the issue in a better way. Thanks!
,
Jan 11 2018
,
Jan 17 2018
We don't think this is a bug. Firefox has the same behavior. When Chrome window is deactivated, "blur" for FirstElement is dispatched, but document.activeElement is still FirstElement. When Chrome window is activated again, Chrome activates document.activeElement first (it means 'focus' for FirstElement), then handles mousedown for SecondElement (it means 'blur' for FirstElement, and 'Focus' for SecondElement). |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jan 11 2018