Manage case summary table styling at top

[demeritcowboy]

Hi,
I see that templates/CRM/Case/Form/CaseView.tpl as of 3.2 now combines the label in the summary table at the top with the actual text value, making it impossible (well, really difficult) to bold or otherwise style the label differently (e.g. Status: Ongoing). Earlier 3.2 betas had it separated like before.

Was this done on purpose? If we can't change it back then does anyone object to at least putting <span>'s around the label/values?

[demeritcowboy]

Similarly, does anybody object to the rows in the Other Relationships table having an id attribute added?

e.g.
<tr id="otherrelationship-15">
where "15" would be the contact id for that row's contact

And also there's no way to tell the two tables in that section apart except for the styling class but it's not so robust to use that for id, so <table id="otherrelationship"> and <table id="caseresources">

[Dave Greenberg]

I can't quite figure out who removed the <label> tags :-( and don't see any reason for it (other than perhaps thinking it's redundant since the <td> has a label class. I think it's fine to put the label tags back (or provide a span w/ a class you can use across those elements - which might make more sense if you're not wanting to style all <label>'s the same way ) - e.g. put this around all of them:

Code: [Select]

<span class="crm-case-summary-label">Case Type:</span>
Regarding the tables, there were some other issues in that section - so I fixed them and added unique class for each table (we're generally using class rather than id for css locators since it allows for a bit more flexibility (according to our css gurus anyway).

    <table class="report-layout otherRelationships">
    <table class="report-layout caseResources">

... and added the contact IDs to the rows for both tables (we're stiil using id's for iterated elements like table rows).

   <tr id="caseResource-81">

(Other fixes: wrong base table class on case resources table, and the add buttons were missing "return false; so user was pushed to top of page prior to redirect).

http://issues.civicrm.org/jira/browse/CRM-6581

I didn't do the label tag fix because I think the span is better but wanted to make sure it meets your use case(s).

[demeritcowboy]

Thanks. Looks good. I added the spans, and also some bolding in civicrm.css to make it like before.

Also I made one change where you had caseResources to globalrelationship to match all the other naming in that section.