chrome.idle.onStateChanged seems not to work on Windows 10
Reported by
junin...@gmail.com,
Mar 23 2018
|
|||
Issue descriptionUserAgent: 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: This bug was reported on Aug 25,2015 already, issue 524663 . But today I found this bug is still not fixed. it is very easy to reproduce by print the log on console. 1.press ctrl-del-alt, the computer screen enters the page of lock options/change pwd/switch users/cancel etc. and currect stat is LOCKED. 2.then press enter key or click "lock" by mouse to confirm lock the screen, but the stat becomes to ACTIVE, that is wired, it should be LOCKED. this is the bug. 3.after pressed enter key to confirm lock screen, and the stat becomes to ACTIVE, then 1 minute later without any actions , the stat becomes IDLE, that is totally wrong again, the stat should be also LOCKED. there should be not ACTIVE, not IDLE. above procedure works correctly on windows 7. What is the expected behavior? What went wrong? the api reported wrong stat value on windows 10. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 64.0.3282.186 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 12 2018
Unable to reproduce the issue on Win-10 using chrome latest stable #65.0.3325.181 and latest canary #67.0.3394.0. Following are the steps followed to reproduce the issue. ------------ 1.Pressed ctrl-del-alt, when chrome is running background. Observed that the computer screen enters the page of lock options/change pwd/switch users/cancel etc. and current stat is LOCKED. 2.Then pressed enter key/clicked "lock" by mouse to confirm lock the screen, and observed that the current state is still LOCKED and not in active state. juninbox@ - Could you please check the issue on latest stable #65.0.3325.181 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
May 31 2018
As there is no response from the reporter from so long, closing this issue as Won't fix. @Reporter: Please feel to raise a new issue if issue is still seen. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Mar 26 2018