http://bugs.winehq.org/show_bug.cgi?id=17627
Summary: winhlp32: clickable area out of sync with hyperlink text Product: Wine Version: 1.1.13 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs@winehq.org ReportedBy: hoehle@users.sourceforge.net
[The following cannot be observed since wine-1.1.14 because of bug #17601. I believe this makes #17601 a blocker for the present issue.]
Between wine-1.1.0 and 1.1.13, after scrolling with keyboard, the mouse sensitive clickable areas stay at their old position, while all text has scrolled! Also, the bottommost line of text may not be refreshed when scrolling upwards. Similar results with PgUp and PgDn, where sometimes half the screen is not refreshed.
OTOH, scrolling via the mouse with the wheel, the scrollbar or the 2 scrollbar arrow buttons works.
It looks like the situation degraded over time -- perhaps several bugs are involved -- however one issue is older than 1.0.1:
In 1.1.0, as well as 1.0.1, the synchronisation between link text and sensitive area is mostly fine -- except when using the cursor keys on a page where all text fits on the page. There, using the up arrow key causes scrolling up, while the clickable areas don't move. If you click inside the window, a cursor appears and the up/down keys cease scrolling and move this cursor instead.
To reproduce, go to a page with links that fits the window (I used winace.hlp). The cursor shall not be visible. Hit the down cursor key. The text scrolls up, while the mouse sensitive areas remain in place (and are functional). Click into the window and the cursor appears. If you move up now, some text scrolls down, but the refresh is very incomplete.
To observe the effect in 1.0.1, you need to scroll up with the down key until after the scrollbar reaches the bottommost position: i.e. you're scrolling farther than would be possible with only the mouse.
Obviously, the fact that 1.0.1 displays scrollbars immediately while 1.1.0 lacks them (cf. bug #14293) does not matter. So this is not the same as bug #14293 which only appeared in 1.1.0.