Chromium does not honor Windows blink rate setting
Reported by
sean...@gmail.com,
Jan 26 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.2992.0 Safari/537.36 Steps to reproduce the problem: 1. Win+S 2. Search for and launch: "Change cursor blink" 3. Change cursor blink rate to: None 4. Launch Chrome 5. Click in an input field or omnibox What is the expected behavior? Cursor does not blink What went wrong? Cursor blinks regardless what the setting is set to Did this work before? No Chrome version: 58.0.2992.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 26 2017
Apparently, you mean the search input field below Google logo on the default new tab page. The cursor blinks there regardless of Windows setting. Whereas omnibox is the address bar on the top and it doesn't blink on my computer. Other input fields on web pages don't blink either.
,
Jan 26 2017
They all blink for me.
,
Jan 26 2017
Is this a regression in chrome 58?
,
Jan 26 2017
Oh, actually the omnibox is the only one blinking in chrome 55, but the other input fields are working correctly.
,
Jan 31 2017
,
Feb 9 2017
Able to reproduce the issue on Windows-10 using chrome stable version 56.0.2924.87 and canary 58.0.3006.0. This is Non-regression issue, observed from M30# 30.0.1595.0 and marking it as Untriaged to get more inputs from dev team. Thanks.
,
Mar 29 2017
,
Jun 6 2017
Any movement on this?
,
Aug 21
Archiving old bugs that haven't been actively assigned in over a year. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Aug 21
Archiving old bugs that haven't been actively assigned in over a year. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Aug 21
Archiving old bugs that haven't been actively assigned in over a year. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sean...@gmail.com
, Jan 26 2017