Created attachment 21975 [details] Image of color issue & element inspector. When trying to customize colors for the staff/admin area you will encounter a color code marked with !important in the CSS staff-global.css. Upon copying the CSS code block and making changes to the color, the staff-global.css color will over ride your select, even with important left on the color statement. Examples: ****My Custom Code:**** #header_search ul.ui-tabs-nav li.ui-tabs-selected { background-color: #FFFFF1; border: 1px solid #800000; !important; border-top: 0 !important; top: -1px; } ****staff-global.css code**** #header_search ul.ui-tabs-nav li.ui-tabs-selected { background-color : #FFFFF1; border: 1px solid #85CA11 !important; border-top: 0 !important; top: -1px; } Notes: I am using the Home › Administration › System preferences > intranetcolorstylesheet option for the CSS file to put my code it. Coding is done via SSH on the system level to my file called custom-login.css. I think the solution is just to remove the !important; statement off the code.
Created attachment 22433 [details] [review] Updated staff-global.css
Created attachment 24411 [details] [review] Bug 11042: Updated staff global.css so that it does not override rules in custom.css Test plan: put \#header_search ul.ui-tabs-nav li.ui-tabs-selected { background-color: #FFFFF1; border: 1px solid #800000; !important; border-top: 0 !important; top: -1px; } in the pref IntranetUserCSS. Go on the intranet main page. Look at the borders of the selected tab in the search header. They should be burgundy-coloured. Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com>
Owen, do you agree with this patch?
I don't find that this patch solves the problem completely: The tab border color only changes on the sides, not on the bottom. Am I not seeing what you're seeing Jonathan? Removing instances of !important is a good goal in general, and I note that the latest version of jQueryUI doesn't have the same use of !important that 1.8.23 has. The real solution to this bug may be an upgrade to jQueryUI.
I confirm this is fixed by bug 11570.