Brave does not honor Windows' blink-rate setting

[jonathansampson]

I received a report from one of our users that Brave was not respecting Windows' Cursor Blink-Rate setting. The blink-rate has the capacity to make some users physically ill (including this individual). This prevents them from using Brave.

The issue is present in Blink, and Blink engineers have been notified.

Firefox:

Brave:

[bbondy]

If chrome supports this bug electron does not, it might be worth cross posting this to electron.

[davidhfo]

+1 for this issue. It is also an obstacle to my use of Brave. The bug is not specific to use on Windows (where it doesn’t honor the registry key HKEY_CURRENT_USER\Control Panel\Desktop\CursorBlinkRate), but is across the board.

It exists on macOS (tried on 10.10.5), where the values in NSTextInsertionPointBlinkPeriodOn and NSTextInsertionPointBlinkPeriodOff are not respected.

The same goes for Linux using GNOME 3, where org.gnome.desktop.interface cursor-blink is not respected.

Note that Chrome on macOS does honor the OS’s settings. I also opened Chrome on a Windows 10 machine and there was no blinking in any text box I tried. In the Chromium issue link posted earlier, the user reporting the problem stated that it was mostly resolved for him, so the issue with cursor blink in Chrome is not affecting everyone on Windows, nor is it across each OS.

I will try various Electron-based apps across OSes to see if they all, like Brave, do not respect cursor blink settings.