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
The way that a selected tab currently remains the displayed tab before and after navigating to a subdataset feels unintuitive. Previously, the "subdatasets" tabs was always the default displayed tab upon navigation to a dataset page. This was changed to keep the last displayed tab as the active one after navigation. But this was particularly in the case when a subdataset was navigated to from the file tree view. It is currently always done, so maybe a more granular approach is necessary? or just revert to the original approach?
The text was updated successfully, but these errors were encountered:
Reverting to original. this also circumvents the issue related to back button navigation: #271. This issue can be closed once the change is merged, but IMO the navigation setup requires more detailed UX testing in order to settle on a setup for the future.
The way that a selected tab currently remains the displayed tab before and after navigating to a subdataset feels unintuitive. Previously, the "subdatasets" tabs was always the default displayed tab upon navigation to a dataset page. This was changed to keep the last displayed tab as the active one after navigation. But this was particularly in the case when a subdataset was navigated to from the file tree view. It is currently always done, so maybe a more granular approach is necessary? or just revert to the original approach?
The text was updated successfully, but these errors were encountered: