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
Currently, we dispatch events from our components to generate new toasts.
We do it using helpers and it looks like this:
notifyError(component,i18n('...'));
When testing cc-orga-member, we realised that people leaving their org wouldn't get the success notification because they are redirected to another page upon leaving: the component from which the toast event is supposed to be dispatched is removed.
This led us to think that any user switching page while an API call is pending (slow network conditions mostly) may not get error / success notifications. Screencast from 2022-12-06 12-03-33.webm
To be discussed
Should we dispatch these events from window instead ?
The text was updated successfully, but these errors were encountered:
Context
Currently, we dispatch events from our components to generate new toasts.
We do it using helpers and it looks like this:
When testing
cc-orga-member
, we realised that people leaving their org wouldn't get the success notification because they are redirected to another page upon leaving: the component from which the toast event is supposed to be dispatched is removed.This led us to think that any user switching page while an API call is pending (slow network conditions mostly) may not get error / success notifications.
Screencast from 2022-12-06 12-03-33.webm
To be discussed
Should we dispatch these events from
window
instead ?The text was updated successfully, but these errors were encountered: