Introduce browser refresh confirmation modal to warn users that files uploads will stop if they refresh they browser
Context
This idea came up when scoping #1495. Users sometimes don't realize that refreshing the browser will cancel file uploads.
Proposal
Add a browser refresh confirmation modal to give user a warning that if they continue with the refresh, the current upload will be be stopped. Apply this to any UI where we have file uploads.
Design
To be determined
Acceptance criteria
-
If user uploads source files from XML, PDF, or Word chapter-processed bulk upload modal and tries to refresh the browser, a pop up warning will appear -
If user uploads source, converted or supplementary files to Word chapter component and tries to refresh the browser, a pop up warning will appear -
If user uploads source, converted, display PDFs, supplementary, or images files to XML book or chapter component and tries to refresh the browser, a pop up warning will appear -
If user uploads source, converted, display PDFs, supplementary, images, or support files to PDF book or chapter component and tries to refresh the browser, a pop up warning will appear
Definition of ready
-
BCMS User Story / Context has been well defined -
The priority of the user story is specified and agreed -
Digital assets added (design, database scheme, mockups etc if relevant) -
Coko Technical Proposal approved by NCBI -
Testable Acceptance Criteria approved by NCBI -
Estimate of effort to complete (time or points) -
The issue has been broken down into development tasks (if necessary) -
Requirements Clarified -
The product owner and development team agree that the user story is ready for development -
NCBI adds “Dev_Ready”
Definition of done
-
All coding tasks are finished and implemented -
QA approved -
Deployed and tested on “ncbidev” (by Coko team) -
Deployed and tested on “ncbi” (by NCBI team) -
Acceptance Criteria Met
Implementation
Implementation (if applicable)
Alternative approaches (if applicable)
It is possible to continue where the user left off in instead of cancelling all file uploads. I.e. if there are 100 files but 10 files have uploaded, the BCMS can save 10 out of the 100.
Scheduling
Dev estimate: 3 day
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking