| Summary: | Navigator Folder Loading "xyz"... Look and Feel | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Simon Kaegi <simon_kaegi> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, Mike_Wilson |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Simon Kaegi
+1 At the very least, we should delay showing that message until a few milliseconds have elapsed - for example, only show the message after 150-200ms if the response hasn't been received by then. For M7 I've added 500ms delay. Not closing this bug though as I think we can do better ;) I've made a similar change in coding.js (and removed a code block that got duplicated and lead to double-loading of the file, must have gotten there by a botched merge). (In reply to comment #3) > I've made a similar change in coding.js (and removed a code block that got > duplicated and lead to double-loading of the file, must have gotten there by a > botched merge). Does anyone else find the above frightening? Two issues: 1) "I've made a similar change" <= not exactly the same? not made the change once and fixed both places? (do we need aspect oriented html?) 2) "gotten there by a botched merge" <= Yikes! Can we go back to CVS? (pretty please) Current behaviour seems pretty reasonable. The old list disappears immediately so I have feedback that it heard me. If it takes more than 500ms I see the "Loading.." message, but otherwise the new content just appears. |