[wp-trac] Re: [WordPress Trac] #8446: post_class() outputs invalid
css class
WordPress Trac
wp-trac at lists.automattic.com
Sun May 3 17:14:03 GMT 2009
#8446: post_class() outputs invalid css class
--------------------------+-------------------------------------------------
Reporter: lilyfan | Owner: nbachiyski
Type: defect (bug) | Status: new
Priority: high | Milestone: 2.9
Component: i18n | Version: 2.7
Severity: major | Keywords: has-patch commit
--------------------------+-------------------------------------------------
Changes (by westi):
* milestone: 2.8 => 2.9
Comment:
The problem for me of switching to ids from slugs is that IDs are fragile
and slugs are not.
If someone has safe slugs then they should be in the classes so that
themes can be written against them.
If we need an extra column in the db to store the calculated safe slug for
css class names then so be it but putting the IDs in just encourages
people to code against them and they are not guaranteed to be consistent
accross multiple installs where you might want to use the same css.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/8446#comment:40>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list