-
Bug
-
Resolution: Fixed
-
Low
-
7.12.0
-
5
-
Severity 3 - Minor
-
2
-
Issue Summary
Livesearch Macro search icon not displayed/aligned correctly when size is 'large'
Steps to Reproduce
- Install Confluence 7.12
- Create a new page and insert 'Livesearch Macro'
- Edit the macro properties - Size to 'large' and save the page
- The macro search icon is not displayed correctly
Expected Results
Livesearch Macro search icon not displayed/aligned correctly when size is large as shown in the attachment.
Actual Results
The search icon should be clearly displayed.
Workaround 1
Change the size to 'medium', the icon is displayed correctly.
Workaround 2
- Navigate to Confluence Administration » General Configuration » Custom HTML
- In the "At end of the HEAD", add the following CSS overrides:
<!-- Workaround for LiveSearch Large - see bug https://jira.atlassian.com/browse/CONFSERVER-65146 --> <style> .search-macro-large .search-macro-query input { padding:2px 12px 2px 30px !important; height:40px !important; font-size:20px !important; font-weight:normal; line-height:1.5 !important; position:relative } .search-macro .search-macro-query input { max-width:none !important } .search-macro-large .search-macro-query .aui-icon { position:absolute; top:20px !important; left:9px; color:#707070 } </style>
- In the "At end of the HEAD", add the following CSS overrides:
- Save and reload the Confluence page that contains the "large" live search
- It should now appear closer to how it looked in previous versions of Confluence
Please note that the "Preview" screen of the "Large" livesearch properties screen is still incorrect but the published viewable page should present itself nicer now
- is duplicated by
-
-
- Closed
-
- mentioned in
-
Page Failed to load
[CONFSERVER-65146] Livesearch Macro search icon not displayed/aligned correctly when size is 'large'
A fix for this issue is available to Server and Data Center customers in Confluence 7.12.3
Upgrade now or check out the Release Notes to see what other issues are resolved.
With the help of our great Support team, we were able to identify this as a regression and are addressing this in our current sprint. It always helps to raise support cases if you see something not looking or behaving as expected to give us an opportunity to understand the impact of an issue and address it, thanks nicolas.belland and stefan.derungs.
Thanks
Makisa | Senior Product Manager, Confluence Server and Data Center
Thank you very much hlam@atlassian.com for workaround number 2 as workaround 1 was not acceptable for us.
But in general I'd agree with nicolas.belland about the classification not being ok (Minor/Long Term Backlog) -> means that sadly this won't get fixed in the next 5-10 years as per past experience on similar classified bugs 
considering the bug should be relatively easy to fix as it was working properly before
Sadly as this issue is classify as "Minor" and in "Long Term Backlog" we will have now to live with it.
What about not breaking the function that works?
Unfortunately we validated and upgraded to 7.12.2
Many thanks for workaround 2 - we use Livesearch an awful lot, so modifying them all was just impossible.