| Summary | Scrolling through messages using down arrow causes unnecessary calls to showMessage |
| Queue | IMP |
| Queue Version | 6.0.3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | aarno.sandvik (at) helsinki (dot) fi |
| Created | 02/12/2013 (4526 days ago) |
| Due | |
| Updated | 02/12/2013 (4526 days ago) |
| Assigned | |
| Resolved | 02/12/2013 (4526 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
around their needs. With a large user base this does come up from time
to time so I'll try to tune the delay.
Response times for showing a message seem to be around 300-600ms. I'll
try to dig deeper to find out what's behind the invalid token error
message.
State ⇒ Not A Bug
in this manner. It is currently set to 0.5 seconds in dimpbase.js:
this.viewport.select(row, { delay: 0.5 });
Queuing is not a viable option, or else a user could be waiting
forever. But we are also NOT going to design our UI around these kind
of users who "mash down" the buttons. They are the exception - the UI
works great for most everyone else.
FWIW, this should not be an issue on a tuned IMP installation since a
show message request should be completed in, at most, 400-500ms.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Scrolling through messages using down arrow causes unnecessary calls to showMessage
Type ⇒ Bug
State ⇒ Unconfirmed
arrow IMP calls showMessage on each message it passes. This generates
a lot of requests that are not needed because the user probably only
wants to see the preview of the message he or she eventually stops on.
Additionally IMP seems not to like this kind of behaviour as it throws
Invalid token exceptions and logs the user out if you keep on
scrolling through the messages.