The record details page re-uses the class results_summary which is semantically incorrect and causes unwanted interactions with the styling of the actual results page which also uses the results_summary class. We should change the instances of the results_summary class to details_summary on this page.
Created attachment 56923 [details] [review] Bug 17514 - Record details page uses incorrect class "results_summary" The record details page re-uses the class results_summary which is semantically incorrect and causes unwanted interactions with the styling of the actual results page which also uses the results_summary class. We should change the instances of the results_summary class to details_summary on this page. Test Plan: 1) Apply this patch 2) Browse to the record details for a bib 3) View the html, note that no elements have the class results_summary, instead, you should see the class details_summary
I agree about the semantic issue, but is the practical aspect of this that it creates problems with customizations? If we have a patch adding details_summary, staff-global.css should be modified to add style for it so that it doesn't break the existing view. As it is, tags, MARC preview, and Holds all display on the same line. This patch must also modify the XSL stylesheet since many of the "results_summary" instances come from there.
Also: This patch modifies the staff client template, but the same issue exists in the OPAC.
I agree with Owen - we are using results_summary in combination with the unique id from the body which avoids any problems. But we'd probably have to change the CSS for quite a few libraries if these classes were changed suddenly.
Kyle, would you agree to make this WONTFIX? (see last comments)
(In reply to Katrin Fischer from comment #5) > Kyle, would you agree to make this WONTFIX? (see last comments) Interpreting 2.5 years of silence as yes :)