Suggested Improvement for Title Text Display

Bug #226898 reported by Dave Jakeman
This bug report is a duplicate of:  Bug #239462: [firefox] tooltips disappear too fast. Edit Remove
4
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Fix Released
Unknown
firefox-3.0 (Ubuntu)
Won't Fix
Wishlist
Unassigned
firefox-3.5 (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Binary package hint: firefox-3.0

Suggested Improvement for Title Text Display
============================================

During the transition from Firefox 2 to 3, the display of title text (as in: <A href="URL" title="page description">) is no longer truncated, bringing Firefox into line with Internet Explorer. This is a most welcome addition. Thanks guys!

The trouble is, Firefox now suffers the same problem that IE does: if the page author puts a large amount of text in the title string, the user doesn't have time to read it. The current title text display model works something like this:

1. User moves mouse pointer over object and then holds still;

2. After something less than one second of no pointer motion, the title text is displayed, wrapping if necessary;

3. A display timer is started;

4. Providing no event or pointer movement occurs, the text displays for a maximum of five seconds;

5. The displayed text disappears and redisplay is disabled;

6. When the pointer next moves, text redisplay is enabled, subject 2 above.

From the end-user perspective, this translates as:

1. Move pointer over object, hold still, wait for title text to appear;

2. Read as much as you can before the five-second timer cuts in;

3. If you finished reading it, you're done!

4. If you didn't, move pointer slightly, hold still, wait for title text to reappear;

5. Quickly find where you left off reading previously and repeat as many times as needed from step 2.

This can be a frustrating experience, so I'd like to suggest two possible display models by way of improvement. The first would be very simple to do, but still only an approximation of what should occur; the second is the proper way to do it:

Alternative 1
-------------

Instead of displaying the title text for a fixed time period of five seconds, display it for four seconds (say) plus some function of the title text length. Through experimentation, the display time could roughly match the time taken for a slow-to-average reader to read the title. For different languages, this would be an approximation.

From the end-user perspective, this would translate exactly as above, but with greater likelihood of being able to read the title text first time through.

Alternative 2
-------------

With the existing model, text display is triggered by zero pointer motion for a fixed time period. Maintain this, but also use pointer movement as the event trigger to vanish the text, disabling redisplay until the pointer moves off the object (moving back over the object would re-enable display).

From the end-user perspective, this would translate as:

1. Move pointer over object, hold still, wait for title text to appear;

2. Read as much of the title text as you want to (ah!);

3. Read something else, or if the title text is obscuring something, move the pointer slightly to make it disappear.

The advantage of the latter is it puts the user back in control of his browsing experience -- just as it should be -- instead of the browser making arbitrary decisions on his behalf. Another advantage is that sometimes, after reading the title text, you don't actually want it to reappear. This solves that. From the user perspective, it would be simpler and rather intuitive too.

Of the two suggested, I would greatly prefer and recommend the latter, but either would be an improvement over the current model and IE.

Hope you can take this one up.

Dave Jakeman

ProblemType: Bug
Architecture: i386
Date: Mon May 5 12:46:50 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: fglrx
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-16-generic i686

Tags: apport-bug
Revision history for this message
Dave Jakeman (davejakeman) wrote :
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Since this is a feature request, you should file a bug about this on https://bugzilla.mozilla.org/. Please search for similar requests before opening a new. Thanks in advance.

Changed in firefox-3.0:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Dave Jakeman (davejakeman) wrote : RE: [Bug 226898] Re: Suggested Improvement for Title Text Display
Download full text (4.9 KiB)

Hi,

This has been progressing as Bug 395668.

Thanks,

Dave

> Date: Thu, 22 Jan 2009 16:16:29 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 226898] Re: Suggested Improvement for Title Text Display
>
> Since this is a feature request, you should file a bug about this on
> https://bugzilla.mozilla.org/. Please search for similar requests before
> opening a new. Thanks in advance.
>
> ** Changed in: firefox-3.0 (Ubuntu)
> Importance: Undecided => Wishlist
>
> ** Changed in: firefox-3.0 (Ubuntu)
> Status: New => Confirmed
>
> --
> Suggested Improvement for Title Text Display
> https://bugs.launchpad.net/bugs/226898
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “firefox-3.0” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: firefox-3.0
>
> Suggested Improvement for Title Text Display
> ============================================
>
>
> During the transition from Firefox 2 to 3, the display of title text (as in: <A href="URL" title="page description">) is no longer truncated, bringing Firefox into line with Internet Explorer. This is a most welcome addition. Thanks guys!
>
> The trouble is, Firefox now suffers the same problem that IE does: if the page author puts a large amount of text in the title string, the user doesn't have time to read it. The current title text display model works something like this:
>
> 1. User moves mouse pointer over object and then holds still;
>
> 2. After something less than one second of no pointer motion, the title text is displayed, wrapping if necessary;
>
> 3. A display timer is started;
>
> 4. Providing no event or pointer movement occurs, the text displays for a maximum of five seconds;
>
> 5. The displayed text disappears and redisplay is disabled;
>
> 6. When the pointer next moves, text redisplay is enabled, subject 2 above.
>
>
> >From the end-user perspective, this translates as:
>
> 1. Move pointer over object, hold still, wait for title text to appear;
>
> 2. Read as much as you can before the five-second timer cuts in;
>
> 3. If you finished reading it, you're done!
>
> 4. If you didn't, move pointer slightly, hold still, wait for title text to reappear;
>
> 5. Quickly find where you left off reading previously and repeat as many times as needed from step 2.
>
> This can be a frustrating experience, so I'd like to suggest two possible display models by way of improvement. The first would be very simple to do, but still only an approximation of what should occur; the second is the proper way to do it:
>
>
> Alternative 1
> -------------
>
> Instead of displaying the title text for a fixed time period of five seconds, display it for four seconds (say) plus some function of the title text length. Through experimentation, the display time could roughly match the time taken for a slow-to-average reader to read the title. For different languages, this would be an approximation.
>
> >From the end-user perspective, this would translate exactly as above, but with greater likelihood of being able to read the title text first time through...

Read more...

Changed in firefox:
status: Unknown → Confirmed
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thank you for finding the right upstream bug.

Changed in firefox-3.0:
status: Confirmed → Triaged
Revision history for this message
Dave Jakeman (davejakeman) wrote :

Apologies for the miscommunication above. The bug reference 395668 is for bugzilla.mozilla.org. It can be viewed at: https://bugzilla.mozilla.org/show_bug.cgi?id=395668

Dave

Changed in firefox:
status: Confirmed → Fix Released
Revision history for this message
Micah Gersten (micahg) wrote :

Firefox 3.0 is only receiving Security Updates and major bug fixes at this point.

Changed in firefox-3.5 (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Changed in firefox-3.0 (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Micah Gersten (micahg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 239462, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.