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
I would like to suggest we move the "Replace" file action to the more options action area as the placement doesn't blend in well with the UI and the iconography is misleading (I've experimented with other icons but without improvement). The action really needs text to explain what the action is and doesn't feel like it should have such a prominent placement.
The "cancel" option which appears after the replacement has taken place can move to the notification, we don't need the magnifying icon as it is already on the image when hovered (even though its not visible to touch devices users can still click on the image to view the full version). We should be able to provide a quick mockup to illustrate the interaction and I'm open to any other ideas instead.
Existing view:
The text was updated successfully, but these errors were encountered:
Hope you don't mind me chipping in here. I just stumbled upon this thread after spending a while trying to find the 'replace' feature in AssetAdmin after finding it in the code. The relocation to the more options area sounds an improvement
I would like to suggest we move the "Replace" file action to the more options action area as the placement doesn't blend in well with the UI and the iconography is misleading (I've experimented with other icons but without improvement). The action really needs text to explain what the action is and doesn't feel like it should have such a prominent placement.
The "cancel" option which appears after the replacement has taken place can move to the notification, we don't need the magnifying icon as it is already on the image when hovered (even though its not visible to touch devices users can still click on the image to view the full version). We should be able to provide a quick mockup to illustrate the interaction and I'm open to any other ideas instead.
Existing view:

The text was updated successfully, but these errors were encountered: