Closed RobAndrewHurst closed 2 weeks ago
Going back into draft as discussed in the meeting to refactor all the elements to use dialog instead of modal.
The modal.mjs module has been renamed to dialog.mjs. This would also require the helpModal.mjs module to also be renamed to helpDialog.mjs to keep with the naming.
There is no mapp.ui.elements.modal
object anymore but mapp.ui.elemets.dialog
modal -> dialog helpModal -> helpDialog
dialog.close must be executed on close if instance of function.
@dbauszus-glx I have added logic that if the dialog is a modal do not use the shiftContained method to ensure the dialog remains in the map container.
Going back into draft due to the modal mask being a draggable element.
The modal Dialog will now append to the body of the document. The user will not be able to adjust the position of the modal in the window. The close button will always appear on a modal.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Description
Before going into the PR we need to understand what the Dialog/Modal actually are. Simply put a
Dialog
is a pop up that appears on the current page. AModal
is the same thing however it is designed to take control over the entire page not allowing the user to interact with other elements until theModal
is closed.<div>
element in the modal creation with the<dialog>
element.<dialog>
element has two modes Dialog/Modal..show()
or.showModal()
modal.dialog
which will control the class and the show method for the<dialog>
element. This will default to true.close()
method that is part of thedialog
&modal
have been introduced.modal-map
(Used for the no locales found Modal) has been established.GitHub Issue
1124
Type of Change
How have you tested this?
Test this with any form of modal. Please check for any odd behaviours.
Testing Checklist
Code Quality Checklist