Closed (fixed)
Project:
Project issue tracking
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Minor
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
25 Sep 2013 at 20:41 UTC
Updated:
4 Jan 2014 at 03:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jthorson commentedTagging. Consistency is good.
Comment #2
helmo commented@webchick: can you link a page where status, priority or category are capitalized?
Comment #3
webchickYes, the link in the original post is such a link. You'll notice the values in each column all start with a capital letter, except for the "Component" values.
Comment #4
jthorson commentedComment #5
jthorson commentedTaking this
Comment #6
helmo commentedAh, I see.
As components are user configurable per project I guess this would involve updating this for the drupal core project in the database.
Comment #7
webchickYeah. Not sure it's worth it, TBH — I categorized this as "minor" for a reason. :) But if there's an existing migration function around that ucfirst()s things that could be applied to the component values, it'd help with consistency.
Comment #8
jthorson commentedPatch does it with a css text-transform ... but yes, we should consider whether we actually want to automatically capitalize the first letter of all components.
Comment #9
jthorson commentedBah ... drupal.org likes losing patch files when you change the project assignment in the same edit. :(
Comment #10
tvn commentedThis is *really* not a launch blocker. Since there is a patch already, let's commit it. But anything else should be done post launch.
Comment #11
drummCommitted.
Comment #12
webchickAwesome, thanks!
Comment #14
dwwNote: people are complaining about this and there's a call to revert this patch:
#2125307: Change component fields back to lower case