Change the default value of "layout.accessiblecaret.timeout_ms" to 0

RESOLVED FIXED in Firefox 49

Status

()

Core
Selection
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: TYLin, Assigned: TYLin)

Tracking

(Blocks: 1 bug)

Trunk
mozilla49
Points:
---

Firefox Tracking Flags

(firefox49 fixed)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

Hiding the caret in cursor mode after three seconds is a b2g spec. I'd like to make the caret persist by default in all platforms, which is a least surprise behavior. Firefox Android does this, too.
Created attachment 8746510 [details]
MozReview Request: Bug 1268410 - Change the default value of "layout.accessiblecaret.timeout_ms" to 0.

That is, the single caret in cursor mode will always persist on all
platforms as on Firefox Android.

Review commit: https://reviewboard.mozilla.org/r/49445/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/49445/
Attachment #8746510 - Flags: review?(mats)
Comment on attachment 8746510 [details]
MozReview Request: Bug 1268410 - Change the default value of "layout.accessiblecaret.timeout_ms" to 0.

https://reviewboard.mozilla.org/r/49445/#review46291
Attachment #8746510 - Flags: review?(mats) → review+

Comment 3

2 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/414529119026

Comment 4

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/414529119026
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox49: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Hiding the cursor on Firefox for Android was a CPU usage/battery win. I don't think we want to revert this.
Flags: needinfo?(snorp)
Kevin, perhaps you're thinking of the blinking text input caret?
I don't see why the non-animated "layout.accessiblecaret" selection carets
should consume any CPU.
Flags: needinfo?(kbrosnan)
I was. Sorry.
Flags: needinfo?(snorp)
Flags: needinfo?(kbrosnan)
You need to log in before you can comment on or make changes to this bug.