Bug #2598
Bug #2596: Implement missing browse quirks.
Adding new row in REPLACE mode causes quirk
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
06/26/2015
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
History
#1 Updated by Stanislav Lomany almost 9 years ago
Scenario:
┌───────────────────────────┐ │┌─────────────────────────┐│ ││ f1 f2 ││ ││ ───────────────────── ││ ││* 1 text10 ││ ││* 2 text20 ││ ││* 3 text30 ││ ││*> 4 text40 ││ ││* 5 text50 ││ ││* 6 text60 ││ │└─────────────────────────┘│ └───────────────────────────┘
After the new row has been added and the value was manually updated:
┌───────────────────────────┐ │┌─────────────────────────┐│ ││ f1 f2 ││ ││ ───────────────────── ││ ││* 1 text10 ││ ││* 2 text20 ││ ││*> 333 text30 ││ ││* 4 text40 ││ ││* 5 text50 ││ ││* 6 text60 ││ │└─────────────────────────┘│ └───────────────────────────┘
After scrolling out of the view and then back again:
┌───────────────────────────┐ │┌─────────────────────────┐│ ││ f1 f2 ││ ││ ───────────────────── ││ ││*> 1 text10 ││ ││* 2 text20 ││ ││* 3 text30 ││ ││* 333 text30 ││ ││* 4 text40 ││ ││* 5 text50 ││ │└─────────────────────────┘│ └───────────────────────────┘
So the new row was actually added, but the rows above it were not shifted properly.
Reproduction - uast/browse/brws-offset6.p:
esc-R, a, 222, down to 6, down (note we have two rows number 6), down, up to 222.