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
Observed behavior (please include a screenshot if possible)
In some browsers (Firefox?), when the user closes the tab/window or navigates away from datatools, componentWillUnmount will not necessarily be triggered, and changes to feed source labels in the "General Settings" tab may be lost. The correct DOM event to handle is sendBeacon, which is currently not compatible with datatools server (only unauthenticated POST requests are allowed when sendBeacon is triggered).
Expected behavior
Changes to labels should be persisted.
Steps to reproduce the problem
Set up labels in a project.
Open a feed source and go to the "General Settings" tab.
Tick one or more labels
Close the browser tab
Reopen the feed source general settings in another tab
Notice the changes to labels were not persisted.
Any special notes on configuration used
n/a
Version of datatools-ui and datatools-server if applicable (exact commit hash or branch name)
Current versions of datatools (both UI and server)
The text was updated successfully, but these errors were encountered:
Observed behavior (please include a screenshot if possible)
In some browsers (Firefox?), when the user closes the tab/window or navigates away from datatools,
componentWillUnmount
will not necessarily be triggered, and changes to feed source labels in the "General Settings" tab may be lost. The correct DOM event to handle issendBeacon
, which is currently not compatible with datatools server (only unauthenticated POST requests are allowed whensendBeacon
is triggered).Expected behavior
Changes to labels should be persisted.
Steps to reproduce the problem
Any special notes on configuration used
n/a
Version of datatools-ui and datatools-server if applicable (exact commit hash or branch name)
Current versions of datatools (both UI and server)
The text was updated successfully, but these errors were encountered: