Bug 1724405 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Here is a profile of starting Firefox and doing nothing with it. It shows about:home and the caret keeps blinking in the url bar forever: https://share.firefox.dev/3AgOoy5

Each time the caret visibility changes, there's activity in the main thread, the Renderer thread and the Compositor thread: https://share.firefox.dev/3fFblmG

Could this be changed to a compositor animation?

Also, it seems most platforms limit the blinking duration.

On Windows, there's a `Computer\HKEY_CURRENT_USER\Control Panel\Desktop\CaretTimeout` registry setting (defaulting to 5000ms) which makes the caret stop blinking after 5s.

On GTK there's a `gtk-cursor-blink` setting (https://docs.gtk.org/gtk3/property.Settings.gtk-cursor-blink.html) which seems to default to 10, for 10s after which the caret stops blinking.

Bug 1159263 already added support for a pref that makes the caret stop blinking after some time, but it's only enabled on Android.
Maybe we could enable this on desktop too?
Here is a profile of starting Firefox and doing nothing with it. It shows about:home and the caret keeps blinking in the url bar forever: https://share.firefox.dev/3AgOoy5

Each time the caret visibility changes, there's activity in the main thread, the Renderer thread and the Compositor thread: https://share.firefox.dev/3fFblmG

Could this be changed to a compositor animation?

Also, it seems most platforms limit the blinking duration.

On Windows, there's a `Computer\HKEY_CURRENT_USER\Control Panel\Desktop\CaretTimeout` registry setting (defaulting to 5000ms) which makes the caret stop blinking after 5s.

On GTK there's a `gtk-cursor-blink-timeout` setting (https://docs.gtk.org/gtk3/property.Settings.gtk-cursor-blink-timeout.html) which seems to default to 10, for 10s after which the caret stops blinking.

Bug 1159263 already added support for a pref that makes the caret stop blinking after some time, but it's only enabled on Android.
Maybe we could enable this on desktop too?

Back to Bug 1724405 Comment 0