While it does make the rendering consistent, I took a different approach to addressing this problem. Rather than following the existing approach in the templates of using <em> tags and CSS classes like "bold" that effectively hardcode presentation-based style decisions into the templates (and thus rendering the value of CSS null), I defined two new CSS classes: "record_author" and "record_title", and applied those classes to both the search results table and the browse results table.
With this branch, a site could decide to remove "font-style: emphasis;" from the style.css definition for record_author, and it will be reflected in both search results pages.
Would you be interested in signing-off on this branch?
Hi Yamil: Thanks for the branch!
While it does make the rendering consistent, I took a different approach to addressing this problem. Rather than following the existing approach in the templates of using <em> tags and CSS classes like "bold" that effectively hardcode presentation-based style decisions into the templates (and thus rendering the value of CSS null), I defined two new CSS classes: "record_author" and "record_title", and applied those classes to both the search results table and the browse results table.
With this branch, a site could decide to remove "font-style: emphasis;" from the style.css definition for record_author, and it will be reflected in both search results pages.
Would you be interested in signing-off on this branch?
See user/dbs/ tpac_author_ name_style in the working repository: http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/tpac_ author_ name_style