Tim Kaddoura's dashboard

This is not a complete fix - please see my comment here – Tim Kaddoura, on July 02, 2009 16:33

The 2.3.3 plugin update indeed fixes the issue but contains a silly schoolboy mistake - namely to have copy/pasted Ryan's CSS workaround verbatim which means even the color (#3355ff) is hard coded!

With the color being hard coded, the deck/card does not adhere to the global/space color scheme and causes the end-user to always have to explicitly set the color.

Please upload a revised version where the color is set to "$action.navBackgroundColor" - which would make the CSS code look like:


.deck .tabBar .tab a {
background: $action.navBackgroundColor;
}

.deck .tabBar #current.tab a {
background: $action.navBackgroundColor;
border: 1px solid $action.navBackgroundColor;
border-bottom: solid $action.navBackgroundColor;
}

.deck .cards.tabbed {
border: 1px solid $action.navBackgroundColor;
}


NOTE Ryan's CSS Workaround missed the second CSS line shown in the code above in the ".deck .tabBar #current.tab a" CSS block! Please don't forget that line!

You don't have to modify the composition plugin jar file and upload a modded version as Ryan suggested to make the workaround successful. An easy peasy lemon squeezy fix is to take the style addon that Ryan listed here and add that CSS chunk to the space stylesheet as seen in the following screenshot:



This worked for me like a charm without having to modify the jar at all. Of course, you can add this to the global space stylesheet as well should you have the composition macro peppered in the entire wiki site...