In all XSLT for record display, fields are created with <span class="results_summary> except in UNIMARC intranet where there is just <li>.
Created attachment 107223 [details] [review] Bug 26049: Replace li with span class results_summary in UNIMARC intranet XSLT In all XSLT for record display, fields are created with <span class="results_summary> except in UNIMARC intranet where there is just <li>. This allows a better CSS customisation and closer code in files for OPAC and intranet. Actually li gets diplayed with a dot at each line, we don't want this. Test plan : 1) For each modified file run 'xsltproc file.xsl' and see there is no error 2) Use default XSLT in all system preferences 3) Perform a search and check display with and without patch 4) Click on a record to see details and check display with and without patch
Created attachment 110020 [details] [review] Bug 26049: Replace li with span class results_summary in UNIMARC intranet XSLT In all XSLT for record display, fields are created with <span class="results_summary> except in UNIMARC intranet where there is just <li>. This allows a better CSS customisation and closer code in files for OPAC and intranet. Actually li gets diplayed with a dot at each line, we don't want this. Test plan : 1) For each modified file run 'xsltproc file.xsl' and see there is no error 2) Use default XSLT in all system preferences 3) Perform a search and check display with and without patch 4) Click on a record to see details and check display with and without patch Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Tested with a UNIMARC sandbox from Biblibre :)
Created attachment 110248 [details] [review] Bug 26049: Replace li with span class results_summary in UNIMARC intranet XSLT In all XSLT for record display, fields are created with <span class="results_summary> except in UNIMARC intranet where there is just <li>. This allows a better CSS customisation and closer code in files for OPAC and intranet. Actually li gets diplayed with a dot at each line, we don't want this. Test plan : 1) For each modified file run 'xsltproc file.xsl' and see there is no error 2) Use default XSLT in all system preferences 3) Perform a search and check display with and without patch 4) Click on a record to see details and check display with and without patch Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Trivial fix that brings this inline with the rest of the ecosystem. No regressions, Passing QA
Pushed to master for 20.11, thanks to everybody involved!
backported to 20.05.x for 20.05.05
backported to 19.11.x for 19.11.11
Backported to 19.05.x branch for 19.05.16