[wp-trac] [WordPress Trac] #27159: Removing TinyMCE buttons to improve user experience
WordPress Trac
noreply at wordpress.org
Sat Oct 15 01:54:15 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-patch needs-user-testing | Focuses: ui,
| administration
--------------------------------------------+------------------------------
Changes (by hugobaeta):
* keywords: needs-patch needs-screenshots needs-research needs-user-
testing => needs-patch needs-user-testing
Comment:
I'd like to see this ticket move along, so circling back to the last round
up of proposed changes, this is the list:
1. move `formatselect` to first position on top row and remove Heading 1.
(And consequently allow for #38049 and #38050 to move forward as well) -
The importance of this select is too great to be buried in the kitchen
sink.
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.
- remove `alignjustify` - same justfication as above, yet in this case
theres no friction for removal.
- 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 really really like to push the removal of the text colors button
entirely, and leave it to plugin territory (as @mrwweb said, #38050 might
help push that too), but we should move that one over to a new ticket. So
that list above is what I'd like to see in a patch for 4.7 inclusion.
This is the intended outcome for now:
[[Image(https://cldup.com/lM0MVsAzpI.png)]]
Does anyone have bandwidth to make a patch for this within the next few
days? If we don't get something in before next week's core chat, this
likely won't make it into core for 4.7. cc/ @mrwweb @iseulde @azaozz
--
Ticket URL: <https://core.trac.wordpress.org/ticket/27159#comment:93>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list