[wp-trac] [WordPress Trac] #23537: Require attributes, not classes
WordPress Trac
noreply at wordpress.org
Tue Feb 19 22:44:40 UTC 2013
#23537: Require attributes, not classes
-----------------------------+------------------------------
Reporter: ryanve | Owner:
Type: feature request | Status: reopened
Priority: normal | Milestone: Awaiting Review
Component: Template | Version:
Severity: normal | Resolution:
Keywords: |
-----------------------------+------------------------------
Changes (by Otto42):
* status: closed => reopened
* resolution: invalid =>
* milestone: => Awaiting Review
Comment:
Sorry, I misunderstood the post. This is fine for core trac.
I don't see that moving all the attributes into the realm of filters is
really desirable or necessary, unless core itself is going to add more
than the class's (or language in the case of the html tag). The theme
itself can easily add its own attributes directly, making them use a
filter to do so is a bit unusual, at best. It's abstraction without a
purpose for it.
Just my 2 cents. Show me a reason to do this and I'll reverse position.
But I don't see many plugins needing to modify anything other than the
classes for those cases, 99% of the time, and core itself has absolutely
no need to do so.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23537#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list