[wp-trac] [WordPress Trac] #11273: Comments: Edit button is not necessary with Quick Edit button
WordPress Trac
wp-trac at lists.automattic.com
Fri Mar 5 14:23:09 UTC 2010
#11273: Comments: Edit button is not necessary with Quick Edit button
-------------------------+--------------------------------------------------
Reporter: lloydbudd | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Comments | Version: 2.9
Severity: normal | Resolution: wontfix
Keywords: |
-------------------------+--------------------------------------------------
Comment(by caesarsgrunt):
Replying to [comment:26 jane]:
> We are past feature freeze for 3.0, so anything that hasn't already been
agreed upon by the lead developers as a task it too late for this version.
Certainly, but the normal way of punting a ticket is to change it to the
next version (or, slightly contentiously, to Future Release) rather than
just close it as ''wontfix'' which means, believe it or not, that it has
been decided not to fix it.
> If two people have a differing opinion on what is more usable, the
answer is to test it with real users. Not with one person's clients, but
in regular usability testing with a broad range of users. Action links on
admin screens were a big part of the testing on 2.5, and the way we
designed 2.7 (which is what this thread is about, the 2.7 action link
design) was based purely on that testing. If you would like to suggest
another round of testing, that would be fine, but saying your opinion of a
usability "bug" is more valid than the formal testing we did is just as
aggravating. You assume decisions I promote are based on my opinion, and
sometimes that's the case, but more often (and in this case) it's based on
testing.
Sorry, I didn't know you had done specific testing regarding the issue of
removing the Edit link, since you never mentioned this. perhaps you would
post the results, or give us a link if they are already online?[[BR]]
Nor had I realised that this action link design was a specific part of the
design for 2.7; I had assumed it was just an artifact from the combination
of the old edit system and the new Quick Edit system. Again, you didn't
mention this when closing the ticket.[[BR]]
Further, as anyone reading the ticket and comments can see, this is not
merely my opinion against usability test results. This is the opinion of
everyone else involved in the ticket except you, against what was
presented as your opinion but you are now saying is based on UX testing.
Either way, the opinions of a group of WP contributors should be
considered and respected, even if it is eventually overruled by UX
testing.
> And in some cases, a decision may be made not based only on what
functionality exists today, or through plugins, but based on where we
think the functionality will be going. If people missed a discussion or
background on a decision (no one is involved in every single discussion in
IRC, wpdevel, forums, hackers, ui group, etc) and think a decision the
lead team has made is bad, if the person would ask why a decision had been
made before complaining about it and saying it is ill-considered, maybe we
could avoid some of this contention.
This is not a one-off issue, it's a widespread opinion that the core devs
are heavy handed in closing tickets they don't personally agree
with.[[BR]]
If you consider this opinion unjustified it is up to you, the core devs,
to fix it. Have you considered the fact that maybe it should be you, when
you close a ticket, who should explain why "why a decision had been made"
in order to avoid some of this contention?[[BR]]
In this case, for example, you clearly presented the decision as a
personal one. If that was not the case, you have unnecessarily created a
bad impression of yourself as a core dev, which you could have avoided by
behaving in a more professional manner by explaining that it was in fact a
team decision based on UX testing (if this is really the case).[[BR]]
It's no use blaming everyone else. Look at the root of the
misunderstanding.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/11273#comment:27>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list