You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
click "dimmer", ie. black backgound to trigger modal close
notice "original dimmer" is shortly displayed, ie. modal with "1" text
When modal is closed (step 2) using modal close button, the unwanted step 3 does not happen.
The issue is "modal element" attaches events to "dimmer element", but when "modal element" is removed from DOM, the events are still attached.
In atk4/ui we need this to be able to reload whole modal - atk4/ui#2262.
I would expect Fomantic-UI modal module to behave like this:
When modal module is initialized (line 23 in repro), check the modal state based on classes (set on line 21) and when the state is "active", it means the modal is "active and shown" (like if $modal.modal('show') was called, but without flashing) and the previous modal/dimmer should be fully garbage collected in favor of the new one.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Feature Request
Steps to reproduce:
When modal is closed (step 2) using modal close button, the unwanted step 3 does not happen.
The issue is "modal element" attaches events to "dimmer element", but when "modal element" is removed from DOM, the events are still attached.
In atk4/ui we need this to be able to reload whole modal - atk4/ui#2262.
I would expect Fomantic-UI modal module to behave like this:
When modal module is initialized (line 23 in repro), check the modal state based on classes (set on line 21) and when the state is "active", it means the modal is "active and shown" (like if
$modal.modal('show')
was called, but without flashing) and the previous modal/dimmer should be fully garbage collected in favor of the new one.The text was updated successfully, but these errors were encountered: