| Summary | Inbox becomes blank when rapidly displaying several messages |
| Queue | IMP |
| Queue Version | 6.2.2 |
| Type | Bug |
| State | Stalled |
| Priority | 2. Medium |
| Owners | |
| Requester | o+horde (at) immerda (dot) ch |
| Created | 09/17/2014 (3892 days ago) |
| Due | |
| Updated | 01/08/2015 (3779 days ago) |
| Assigned | 09/19/2014 (3890 days ago) |
| Resolved | 01/08/2015 (3779 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Stalled
Without a reliable way of reproducing, nothing more can be done here
so marking as stalled.
Keyboard navigation was already rewritten in IMP 7 awhile back, so
maybe that will help you out in the future.
We are still plagued by the problem!
see "This folder contains no messages".
- i can most easily trigger it with chrome
- the triggering viewPort response stands out by having rowlist_reset: true
- the condition is followed by "Uncaught TypeError: Cannot set
property 'VP_rownum' of undefined"
(https://github.com/horde/horde/blob/bb18b225fb770ce54b6b83d0313b710d7b954908/imp/js/viewport.js#L1518), this is however not the cause but merely a secondary
effect
here is an example viewPort response triggering it:
/*-secure-{"response":true,"tasks":{"imp:viewport":{"label":"a
label","totalrows":1108,"rowlist_reset":true,"rowlist":{"1105":52,"1104":53,"1103":54,"1102":55,"1101":56,"1100":57,"1099":58,"1098":59,"1097":60,"1096":61,"1095":62,"1094":63,"1093":64,"1092":65,"1091":66,"1090":67,"1089":68,"1088":69,"1087":70,"1086":71,"1085":72,"1084":73,"1083":74,"1082":75,"1081":76,"1080":77,"1079":78,"1078":79,"1077":80,"1076":81,"1075":82,"1074":83,"1073":84,"1072":85,"1071":86},"data":{"1105":{"flag":["\\seen","list"],"size":"12
KB","date":"03.09.2014",
[...]
},"cacheid":"VTExNTcsVjEyNjA5NzY5ODAsSDYyOA==|12|1|D261","view":"SU5CT1guZnVsbGRpc2Nsb3N1cmU"}}}*/
State ⇒ Feedback
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Inbox becomes blank when rapidly displaying several messages
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
2) Use the arrow down keys to navigate the inbox: continue going down
the list ~2 entries per second for around 3 seconds and then stop.
3) Suddenly the inbox becomes empty, no mails are displayed anymore.
4) imp has to be reloaded before the folder is displayed non-empty again.
The bug is somewhat fragile to reproduce.
For one it is most easily triggered when a user didn't log in for a
while (probably due to caching), it seems to rely on the imap backend
being able to server every request fast enough and the speed at which
mails are navigated.
Even so i can trigger it regularly and users report it regularly. we
cannot exactly pinpoint the release where this was introduced.
Please let me know if you can reproduce it.