Bug 252412 - Screen jumps (scrolls) down when typing after scrolling up
Summary: Screen jumps (scrolls) down when typing after scrolling up
Status: RESOLVED DUPLICATE of bug 258913
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-26 12:25 UTC by niburu1
Modified: 2012-11-08 09:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.8.5


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description niburu1 2010-09-26 12:25:11 UTC
Version:           2.1b4 (using KDE 4.5.1) 
OS:                Linux

If I scroll down so that the cursor is located above the last VISIBLE line of the page, when I start typing the screen jumps up. Where the screen jumps to depends on where it was previously (i.e. it doesn't jump to a fixed place).

It did not do this previously on my system before I installed some updates from the Kubuntu 10.04 backports repository.

Reproducible: Always

Steps to Reproduce:
1. Open or create a new document that has more than a page of text.
2. Scroll down so the cursor is located above the last VISIBILE line (not necessarily the last absolute line of the document).
3. Type something.

Actual Results:  
The screen jumps up.

Expected Results:  
The screen doesn't jump.
Comment 1 Michel Ludwig 2010-10-02 17:14:41 UTC
Sorry, but I can't reproduce this here. But just in case I'm forwarding this to KatePart.
Comment 2 niburu1 2010-10-02 17:21:44 UTC
It still occurs on my system after an update to Kubuntu 10.10 RC. It looks like it might be a bug located in the "Autocenter cursor (lines)" feature.
Comment 3 Christoph Cullmann 2012-11-07 23:19:28 UTC
I can't reproduce either, even not if I say auto center for example 1 or 3 lines.
Comment 4 Dominik Haumann 2012-11-08 09:43:41 UTC
Christoph, you fixed that yourself for KDE 4.8.5 :-)

*** This bug has been marked as a duplicate of bug 258913 ***