Bug 511109 - Message display scrolls to top when link clicked
Message display scrolls to top when link clicked
Product: Fedora
Classification: Fedora
Component: gtkhtml3 (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-07-13 13:25 EDT by Matthew Saltzman
Modified: 2009-07-13 15:49 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-13 15:49:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 588480 None None None Never

  None (edit)
Description Matthew Saltzman 2009-07-13 13:25:52 EDT
Description of problem:
When I click an embedded link in the middle of a long message or digest, the link opens in a browser, but the message scrolls back to the top and I have to manually scroll back down to where I was reading.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Read a long message, scroll the top of the message out of the display window
2. Click a link
Actual results:
Message scrolls back to top

Expected results:
Message display window does not change

Additional info:
I use the wide view, with the message window at the right of the display.

This has happened for several versions, back to at least F9.
Comment 1 Matthew Barnes 2009-07-13 13:41:52 EDT
Check whether you have Caret Mode enabled:

   View -> Caret Mode (F7)

Disable it if you do.  It causes all sorts of weird glitches like this.
Comment 2 Matthew Saltzman 2009-07-13 14:59:43 EDT
OK, yes I did have it on.  Turning it off stops the behavior.

What's it supposed to do?
Comment 3 Matthew Barnes 2009-07-13 15:49:23 EDT
It's an accessibility feature in GtkHTML, but it's never really worked right.
And to be honest, it probably won't be fixed before we switch to WebKit, which hopefully handles it better.

Regardless, I sent it upstream so it's at least filed:

Note You need to log in before you can comment on or make changes to this bug.