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
In CMS 5 when dragging files or folders to a new folder (either by dragging them onto a folder specifically or dragging them into the "back" button in the asset admin to go up to the parent folder), the asset admin would navigate so we're now viewing that folder.
In CMS 6 we remain inside the original folder where the files used to be.
It's possible the new behaviour is actually better, in which case we can call it a feature and document it in the changelog (and make sure any dead code from the old behaviour is removed) - but for now I'm assuming it was an unintended bug and regression.
Acceptance criteria
Get UX advice from the design team about which behaviour is better
If the new behaviour is better:
the change is documented in the changelog
dead code related to the old behaviour is removed
If the old behaviour is better:
The regression is fixed
A behat test is created to test whichever behaviour we end up using
The text was updated successfully, but these errors were encountered:
In CMS 5 when dragging files or folders to a new folder (either by dragging them onto a folder specifically or dragging them into the "back" button in the asset admin to go up to the parent folder), the asset admin would navigate so we're now viewing that folder.
In CMS 6 we remain inside the original folder where the files used to be.
It's possible the new behaviour is actually better, in which case we can call it a feature and document it in the changelog (and make sure any dead code from the old behaviour is removed) - but for now I'm assuming it was an unintended bug and regression.
Acceptance criteria
The text was updated successfully, but these errors were encountered: