Notification polling duplicated on turbolinks navigation
since notification component is re-mounted, polling is re-initialised whenever turbolinks navigation occurs.
does this effect other components such as toast notifications? or maybe even host power ?
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4588 added
- Legacy Backlogs Release (now unused) set to 240
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #20334: notification api promise was called incorrectly. added
- Category set to Notifications
- Is duplicate of Bug #18327: Notification polling request should not be initiated if there is an open turbolinks operation added
Also available in: Atom