Bug 143936 - pressing enter at top of document: awkward scrolling (regression!)
Summary: pressing enter at top of document: awkward scrolling (regression!)
Status: RESOLVED DUPLICATE of bug 146300
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-07 19:25 UTC by Maciej Pilichowski
Modified: 2007-12-07 11:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-04-07 19:25:20 UTC 
Version:            (using KDE KDE 3.5.6)
Installed from:    SuSE RPMs

I just upgraded Kate to newer revision and there is a new bug introduced.

=== denotes boundaries of the document
--- denotes boundaries of the window
| denotes text cursor

Let's say you have:

===---
|A
===

---

when you press enter you should get:

===---

|A
===
---

but instead you get:

===
---
|A
===

---

Newlines are added at the top (ok) but also the text is scrolled down!
Comment 1 Thomas Friedrichsmeier 2007-12-07 00:55:09 UTC 
Same as bug #146300 . Actually 146300 is the duplicate of this one, but marking it the other way around to gather all the info in one report.

*** This bug has been marked as a duplicate of 146300 ***
Comment 2 Maciej Pilichowski 2007-12-07 07:55:28 UTC 
Thomas, what "all the info"? Both repports discuss the same details -- I would not like to see statistics with all duplicates on my side.
Comment 3 Thomas Friedrichsmeier 2007-12-07 11:43:55 UTC 
Well, it already has the line that this is fixed in KDE 4 (and I'll close it due to that, soon), and I had already started marking other bugs as dupes of it, so those are listed there.

I'm not aware of any stats of duplicate reporters, and if there is one, I sure hope it's smart enough to take the order of submissions into account (and if it's not, submit a bug report on that ;-) ).