[wp-trac] [WordPress Trac] #10753: Introduce smarter TinyMCE menu by reducing inline styles and using content aware styling
WordPress Trac
wp-trac at lists.automattic.com
Wed Sep 9 13:29:43 UTC 2009
#10753: Introduce smarter TinyMCE menu by reducing inline styles and using content
aware styling
-----------------------------------------------------------------------------------------------------------------------------------+
Reporter: micasuh | Owner: azaozz
Type: enhancement | Status: reopened
Priority: normal | Milestone: 2.8.5
Component: TinyMCE | Version: 2.8.4
Severity: normal | Resolution:
Keywords: tinymce, inline style, content aware styling, classes, custom classes, editor, best practices, usability, css, editor |
-----------------------------------------------------------------------------------------------------------------------------------+
Changes (by novasource):
* cc: novasource (added)
* keywords: tinymce, inline style, content aware styling, classes,
custom classes, editor => tinymce, inline
style, content aware styling, classes, custom
classes, editor, best practices, usability,
css, editor
* status: closed => reopened
* resolution: wontfix =>
Comment:
This isn't about a developer's whim. It's about product strategy.
If WordPress aspires to be designer-friendly, it can't arbitrarily decline
web best practices.
Profuse use of inline styles is a bad practice. E.g.,
http://webdesign.about.com/od/css/a/aa073106.htm. WP should not default to
bad practices.
The bad thing about them is that when the user switches the theme all
the styling will disappear.
No:
1. '''Nobody is proposing modifying existing content.''' Already-existing
inline styles will continue to work.
1. '''This would be new CSS classes.''' They cannot affect existing
content except by sheer coincidence.
Styling will continue to work with themes created by responsible
developers who monitor
http://codex.wordpress.org/Migrating_Plugins_and_Themes.
Not only is this enhancement a major strategic improvement, it complies
with WP's own apparent standard at
http://codex.wordpress.org/CSS#WordPress_Generated_Classes.
Force-inserting major CSS in wp_head would be disastrous.
Not disastrous, just not a 2 line patch.
Admittedly, this is a large issue and may may need to be broken down into
smaller issues. But let's not kneejerk a "wontfix" on this.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10753#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list