Comment 9 for bug 1315434

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Making it configurable obviously wouldn't "satisfy all user needs", because only a small fraction of users who might benefit from it would even know the option exists. Fewer still would comprehend *why* it exists, and even fewer than that would be bothered changing it. Making things worse, the added UI complexity would dissuade people from using the more-useful options around it. And the code would be less reliable, because engineers and testers would be allocating the same total amount of time to more code paths. And, after all that, we'd still have to decide what the default setting should be!

So, no, we're not going to make this configurable. Instead let's concentrate on actually fixing the bug.

I don't know how I missed seeing before that the mouse in question "has no time remaining estimate". That should automatically exclude it from being considered as the device that will discharge most quickly.