[wp-trac] [WordPress Trac] #12035: Allow taxonomy privledges to be handled independently of categories

[WordPress Trac]

#12035: Allow taxonomy privledges to be handled independently of categories
-------------------------+--------------------------------------------------
 Reporter:  dd32         |       Owner:  dd32    
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  3.0     
Component:  Taxonomy     |     Version:  3.0     
 Severity:  normal       |    Keywords:          
-------------------------+--------------------------------------------------

Comment(by dd32):

 > What's the argument for showing the UI in a disabled state as opposed to
 not showing it at all

 My reasoning is, The Taxonomy data is public information attached to the
 post, You can physically see the metadata is there, You cannot modify it
 however.

 One example that someone brought up with me in private was having an
 Editor that could accept/reject postings, They wanted to be able to see
 the category data before accepting, but not modify it. While thats a
 specific use case (and one that would require greater plugin modifications
 of core anyway) I didnt see a problem with that.

 If theres a Agreement between someone who can comment on the UI angle that
 hiding the box alltogether would be better, I dont mind that, I was just
 trying to make it as transparent to the public post data as possible,
 whilst still keeping the capabilities in tow.

 > "when I click the checkboxes, nothing happens" than by absence.
 Then the disabled class styling has failed us. Disabled elements are
 something that people should deal with often, it even happens in WordPress
 that some fields are readonly... occasionally.. my point is, that the
 styling for such elements should make it visible that its disabled and
 cannot be modified.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12035#comment:18>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software