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
We use workloadClient.dialog.open for our create dialogs and for a dialog we use to import sample assets. Recently, when we move from a creation experience to sample import or visa-versa, we see a brief blink of the wrong dialog content.
Example flow:
create a decision
import sample data (Note a brief flash of the create decision dialog content)
You can see this in the attached recording.
This has only been happening for the last few weeks. Recently, I changed our call to "workloadClient.dialog.close" to always use CloseMode=2. Before this, we were sometimes having operations fail as the intended dialog was never displayed. Since this change, we do seem to always get the correct dialog but often with the brief display of the WRONG dialog as shown in the recording.
Is there anything you can think of that we might be doing wrong?
Another thing to mention.... probably 2 months ago, we notice that the IFrame created for dailogs is handled differently than before. Before, we could always count on "useState()" hooks to be cleared whenever a dialog is displayed. Now, we have to use an "IntersectionObserver" to manually clear the local useStates or we see information from the previous use of the dialog when we do not want that. My guess is that the Iframe is beging retained and dialogs are not being properly destroyed.
Workload Manifest Schema Version (if relevant)
No response
Your Question
We use workloadClient.dialog.open for our create dialogs and for a dialog we use to import sample assets. Recently, when we move from a creation experience to sample import or visa-versa, we see a brief blink of the wrong dialog content.
Example flow:
You can see this in the attached recording.
This has only been happening for the last few weeks. Recently, I changed our call to "workloadClient.dialog.close" to always use CloseMode=2. Before this, we were sometimes having operations fail as the intended dialog was never displayed. Since this change, we do seem to always get the correct dialog but often with the brief display of the WRONG dialog as shown in the recording.
Is there anything you can think of that we might be doing wrong?
Another thing to mention.... probably 2 months ago, we notice that the IFrame created for dailogs is handled differently than before. Before, we could always count on "useState()" hooks to be cleared whenever a dialog is displayed. Now, we have to use an "IntersectionObserver" to manually clear the local useStates or we see information from the previous use of the dialog when we do not want that. My guess is that the Iframe is beging retained and dialogs are not being properly destroyed.
Any advice is greatly appreciated.
Context / Background
Screen.Recording.2026-03-10.132257.mp4
Additional References
No response