The UI for image generation history is becoming increasingly cumbersome.

### What problem are you experiencing?
More specifically, it's the assets interface, because it allows you to view multiple images at once and the display size is good.

It used to be that you could click an image to view it directly.
Then, clicking an image wouldn't work, and you had to click a small button instead.
Or, you had to click "View More" to enter a secondary image list to view them.
Now, you have to click a secondary menu just to view them.
Even after entering the secondary image list, you still need to click another secondary menu to view the image.

It used to be that you could drag and drop files to save them anywhere.
Then, dragging only saved the view URL, requiring you to "View More" and go into the secondary list to drag and save the image.
Now, dragging from the secondary image list also only saves the view URL.
It now takes many steps just to drag and save an image.

If the use of thumbnail caching was acceptable because it reduced memory usage, in fact, what is being used here is the original image.

Why make something that could be solved in one step increasingly complicated?
Can we return to the era where viewing or saving an image only took one step?

(Machine translation)

### When does this problem occur?

As updates gradually become available.

### How often do you encounter this problem?

Several times per week

### How much does this problem affect your workflow?

Minor annoyance

### Current workarounds

_No response_

### Ideas for solutions (Optional)

Change the drag-and-drop function to drag-and-drop for saving images, rather than dragging and dropping to save as a URL.

### Additional context

_No response_

Start by locating the assets interface and image generation history views described in the issue, then reproduce viewing and drag-and-drop behavior. Compare the current menus and save targets with the requested one-step image viewing and saving workflow; done means images can be viewed and dragged to save directly.

Written by the indexing model from the issue text.