Comment 35 for bug 239462

Revision history for this message
In , Dave Jakeman (davejakeman) wrote :

This was prompted by Comment #30, but is not a direct response to it. It is an attempt to clarify my earlier description, for the benefit of all:

Let's say the object in question is a graphic image of a button. Imagine what happens:

1. Mouse pointer moves over button. At the image boundary, tooltip display is enabled, but won't display until the user holds still.

2. User holds still for the required time (something less than a second, as at present) and the tooltip is displayed.

3. User continues to do nothing with the mouse and so the tooltip continues to display for as long as the pointer remains static, putting the user in direct control of the tooltip display duration.

4. User finishes reading the tooltip.

5. The moment the mouse pointer next moves, as dictated by the user, the tooltip vanishes. That tooltip is now disabled until the mouse pointer crosses (exits) the image boundary and Step 1 recurs (or perhaps just until Step 1 recurs).

At step 5, the tooltip would vanish if the pointer moved only slightly (remaining over the button), or moved off the button completely (see comment #19).

Stripping out the user interaction parts of the above leaves a description of what the software should do.

Hope this is useful.