Fix: Modal Trigger Issue with Top Navigation Enabled #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit addresses a critical issue where modals were not properly triggering or opening when top navigation was enabled in the application. For some reason, when top navigation is enabled, the icon button which triggers the modal needed to be reinitialized using alpine's
x-dataattribute. Users experiencing difficulty in interacting with modals in this scenario should now find the functionality working as expected.Additionally, I have implemented a sticky header for modals when in slide-over mode. This improves the design of the header in the slide-over.
Video
PanelSwitch.mov