[MGNLUI-4173] Provide support for app and sub-app close confirmation requirement Created: 23/Mar/17 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Story Points: | 8 |
| Description |
|
Currently there is no easy way to guard apps/sub-apps close controls with a confirmation dialog, that would warn the users of potential data loss. One can implement such support for the sub-apps, but that would involve overriding of some rather low-level components like SubAppContext itself. There should be a clear API/point of interception where the close event could be aborted. |
| Comments |
| Comment by Mikaël Geljić [ 26/Jun/17 ] |
|
Previous description was a tad more about apps having no way to be properly closed programmatically in the first place (as opposed to sub-apps), if I got things right. On the other hand, I see the need for supporting such means of interception by design (vs. ad-hoc mechanism we have for dialogs & editors). Nothing too dramatic though (for the lack of somewhat more popular requirement or demand). |