After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89290 - URLs sometimes not clickable
URLs sometimes not clickable
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.13.0 betas
Other Linux
: Normal minor
: 0.13.1
Assigned To: Christophe Lambin
Pan QA Team
: 88522 91308 94497 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-07-28 22:44 UTC by Christophe Lambin
Modified: 2006-06-18 04:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christophe Lambin 2002-07-28 22:44:11 UTC
I've noticed some behaviour which could explain why sometimes users find
that URLs are not clickable. The scenario to reproduce with CVS HEAD is this:

1. find an article that has a URL, and is big enough to have a scrollbar
2. display the top of the article
3. mouse over the URL and see the cursor change to a hand (clickable URL)
4. scroll the article one line
5. mouse over the URL and see that it's not clickable
6. move the mouse down to where the URL was before scrolling. The cursor
should change back to a hand

So, it looks like the tags we use to track URLs are calculated based on the
original position, but don't take scrolling into account.
Comment 1 Charles Kerr 2002-07-29 00:42:24 UTC
Chris: Is this the same bug as 88522?
Comment 2 Christophe Lambin 2002-07-29 06:57:23 UTC
Not 100% sure, but looking at the article in that bugreport, I'd say it's pretty likely. 

Comment 3 Charles Kerr 2002-07-29 12:11:21 UTC
*** Bug 88522 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Lambin 2002-08-21 19:57:23 UTC
*** Bug 91308 has been marked as a duplicate of this bug. ***
Comment 5 Christophe Lambin 2002-08-23 22:45:34 UTC
Fixed in CVS.
Comment 6 Christophe Lambin 2002-09-30 18:47:58 UTC
*** Bug 94497 has been marked as a duplicate of this bug. ***