Bug 109497 - konqueror does not scroll inside embedded object to highlight text
Summary: konqueror does not scroll inside embedded object to highlight text
Status: CONFIRMED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 4.5.4
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-23 00:41 UTC by Gioele Barabucci
Modified: 2021-03-21 00:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gioele Barabucci 2005-07-23 00:41:10 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages

Go to this url: http://forums.knoppix-fr.org/viewtopic.php?id=1277 .
You can see that it contains an embedded text object with some code.
Position yourself on the top of the page and search for "route".
Keep searching until you'll be facing the end of the page. Where is "route" it is not here?!?!?!

Indeed "route" in down inside the ebedded text object and konqueror did not scroll that object but the entire page to show it.


This could be related to bug #70072
Comment 1 Christophe Marin 2008-04-16 16:34:40 UTC
This bug is resolved in trunk (rev. 797569)
Comment 2 Germain Garand 2008-04-16 17:06:38 UTC
no, I'm quite sure it is not - though there might exist a duplicate of this bug.

What reporter means is that the first container with scrollbars (containing the word "route") should be scrolled to reveal it, instead of the main document.

Currently, the page is scrolled to the position that the word would occupy if the container did not hide it's content in a scrollable area.
Comment 3 Christophe Marin 2008-04-16 20:54:16 UTC
Indeed, my local testcase wasn't identical. I used textarea instead of div. 

So, confirmed in trunk (rev. 797569). My apologies.
Comment 4 Samuel Brack 2011-01-07 00:20:21 UTC
Confirmed in 4.5.4, updating version.
Comment 5 Justin Zobel 2021-03-21 00:24:54 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.