Make WordPress Core

Opened 14 years ago

Closed 8 months ago

#13392 closed enhancement (fixed)

Image editor UX could be more straightforward

Reported by: simonwheatley's profile simonwheatley Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Media Keywords: needs-patch
Focuses: ui, administration Cc:


The image editor introduced in v2.9 (?) is pretty handy, but I believe the UI needs to be straightforward. Here's some issues which I see, as a starter for discussion, and hopefully later I'll be able to make some quick wireframes to suggest improvements and so everyone can have something to get hating.

The overarching issue is that the UI seems confused when it comes to committing the action you've just taken, for example:

  • To scale an image, you commit the action with a button labelled "Scale".
  • To commit a crop you have to click the crop icon button, which looks like a tool selection button (ala Photoshop) rather than something which commits the change.
  • The Save button is disabled most of the time, for reasons which are unclear, but it's not super obviously styled as disabled.

Separately from the problems of committing actions, the "Apply changes to" panel is kind of stuck down to the right and it's not clear at which points it's having an effect.

There are no messages back to the user to confirm whether actions have or haven't been taken.

Change History (14)

#1 @scribu
14 years ago

  • Keywords ux-feedback added

#2 @scribu
14 years ago

  • Milestone changed from Unassigned to 3.1

#3 @JohnONolan
14 years ago

Hi Simon,
Could I encourage you to come to UI group meetings on Tuesdays for this sort of stuff? Generally we handle the UI/UX ideas and projects over at first, and then once they're signed off we come over to Trac for Teh Code!

#4 @jane
14 years ago

The media uploader redesign we had planed included fixing up the image editing. As Andrew Ozz was coding up the UI, it became clear that the media code was super-convoluted and touched almost every piece of WP, and backwards compatibility was going to be a bear. Mike Adams suggested maybe we should put the UI on hold and plan to attack the media code altogether in a future release. Now that 3.0 is out of the way, we can talk about when we can do the media stuff, but 3.1 is going to be the " release," so media will likely need to wait for 3.2.

#5 @nacin
14 years ago

  • Milestone changed from Awaiting Triage to Future Release

#6 @JohnONolan
14 years ago

  • Keywords needs-ui gci added; ux-feedback removed

#7 @webvitaly
13 years ago

  • Keywords changed from needs-ui, gci to needs-ui gci

Feature request: why loading animation during all actions is showing always above the crop tool? I think, it would be more intuitive, if the animation will appear above specific button of the current action or above the working image.
I am using WordPress 3.3-aortic-desection.

#8 @simonwheatley
11 years ago

  • Keywords close added

This looks fixed to me now.

#9 follow-up: @markoheijnen
11 years ago

Currently I'm working on a complete redesign for the image editor. That is something what is still needed in my opinion. I guess with the new media dialog in 3.5 even more. I'm now learning backbone to make the image editing as a dialog and play with that. Will be releasing that as a plugin. What hopefully I can release before 3.6

#10 @ericlewis
10 years ago

  • Keywords needs-ui gci close removed

Related: #11477

#11 in reply to: ↑ 9 @ericlewis
10 years ago

  • Focuses ui added

Replying to markoheijnen:

Currently I'm working on a complete redesign for the image editor.

Did you make any headway in this regard?

#12 @markoheijnen
10 years ago

No, After the changes in 3.9 I didn't had the time to look at those and build on that. I would love to work on this ticket but would like to see a team around this. I will start joining the Media Component Office Hours on Friday.

#13 @chriscct7
9 years ago

  • Focuses administration added
  • Keywords needs-patch added

#14 @joedolson
8 months ago

  • Resolution set to fixed
  • Status changed from new to closed

Most of these changes were made with #50523. Closing this ticket as fixed; given the significant changes since this ticket, I'd suggest opening a new ticket if there are specific additional changes desired. Thanks!

Note: See TracTickets for help on using tickets.