[wp-trac] [WordPress Trac] #27159: Removing TinyMCE buttons to improve user experience
WordPress Trac
noreply at wordpress.org
Sat Oct 15 23:29:11 UTC 2016
#27159: Removing TinyMCE buttons to improve user experience
--------------------------------+---------------------------------
Reporter: hugobaeta | Owner: hugobaeta
Type: enhancement | Status: assigned
Priority: normal | Milestone: 4.7
Component: TinyMCE | Version: 3.8
Severity: normal | Resolution:
Keywords: needs-user-testing | Focuses: ui, administration
--------------------------------+---------------------------------
Changes (by azaozz):
* keywords: needs-user-testing has-patch => needs-user-testing
Comment:
Replying to [comment:93 hugobaeta]:
> 2. move the `alignleft`, `aligncenter`, and `alignright` to the kitchen
sink - these buttons generate non-semantic inline styles (`<p style="text-
align: right;">`), but since they seem to be popular, until we can figure
out another semantic solution for these, they should at least be moved out
of sight for new users.
As far as I've seen the align-center button is the third most used button
in the editor, after bold and link. Even if we had only three buttons in
the editor, one of them would have been align center. Don't think it is a
good idea to move it to the second row.
For the UX it doesn't matter how it works or what kind of HTML it
generates.
So the options are to either keep the alignment buttons where they are or
separate the align-center button and move align-right and align-left to
the second row. The problem with separating them is that they loose
context. I haven't seen that in any editor, anywhere.
> - Remove `underline` - again, like others, the `underline` button
introduces non-semantic inline styles (`<span style="text-decoration:
underline;">`) and introduces potential accessibility issues when
comparing with links. The `<mark>` html tag has the semantic meaning this
tried to convey, and should be used instead - I created a separate ticket
for that #38315
I'd rather not remove `underline` but replace it with `mark`. Think better
to use #38315 for that.
> Does anyone have bandwidth to make a patch...
Patch is very easy to make. But generally removing things or moving things
around doesn't improve UX. We need to clearly prove the UX is better after
rearranging the buttons. That's what is missing :)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/27159#comment:98>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list