As a WWT user, I want the revision details pop-up to be implemented in an efficient and thoughtful manner, so that I can use the tool with ease.
Background: Quite a lot has changed since the original plan was created for the behavior of the Revision popup. Initially, it was simple and straight forward enough to have the majority of the logic exist in the small widget and update itself. However, as we went into caching promises and adding a model and controller, it is a good time to revisit the internal behavior of the revision popup and the way it presents itself with the cached API promises.
- Investigate the current implementation of the revision details pop-up to determine if:
- There are any architectural issues or concerns that should be addressed
- There are any security issues that should be addressed
- Refactor the relationship between the RevisionPopupWidget, Model and Controller for clarity