If we do this, I'm not sure that 3 seconds is enough for most users. A lot of people don't notice animated pop-ups in the corner of the screen as fast as you or I do. I would advocate for a minimum of 5 seconds, or even a bit longer.

In D10921#215715, @ngraham wrote:

If we do this, I'm not sure that 3 seconds is enough for most users. A lot of people don't notice animated pop-ups in the corner of the screen as fast as you or I do. I would advocate for a minimum of 5 seconds, or even a bit longer.

should be tested... with this code, for.. "reasons", i always wait for 2 timeouts, so would be around 6 seconds tough variable, all depends on the last user activity (one could argue "most of the times" the popup goes up for manual insertion of a thumbdrive, which means no user action at that moment, so the popup would stay "forever" until the user moves the mouse again or types stuff, then the 2*3 seconds timeout starts

In D10921#215717, @mart wrote:

In D10921#215715, @ngraham wrote:

If we do this, I'm not sure that 3 seconds is enough for most users. A lot of people don't notice animated pop-ups in the corner of the screen as fast as you or I do. I would advocate for a minimum of 5 seconds, or even a bit longer.

should be tested... with this code, for.. "reasons", i always wait for 2 timeouts, so would be around 6 seconds tough variable, all depends on the last user activity (one could argue "most of the times" the popup goes up for manual insertion of a thumbdrive, which means no user action at that moment, so the popup would stay "forever" until the user moves the mouse again or types stuff, then the 2*3 seconds timeout starts

That seems fairly reasonable to me.

In D10921#215718, @ngraham wrote:

That seems fairly reasonable to me.

so, what i would like is to have this early in the cycle, so there is plenty of time to test for who has master, or neon devel unstable and still tweak it to be perfect before 5.13 release