[xwiki-devs] [Vote][Proposal] New Skin/ColorTheme Improvements for XE 3.4

Hi, Ludovic suggested we should refresh the Default Color Theme for XE 3.4 with something new. Since (and long before) we dropped support for IE6 and IE7 (XE 3.2) I wanted to add some CSS3 enhancement to our default skin: shadows, gradients, round corners, etc. So this is a good time to make a proposal that integrates some CSS3 (gradients on menus, panels, tabs, buttons, forms; text-shadows; box-shadows; border-radius;) and a new ColorTheme into Colibri skin: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/34Proposal There are 3 directions that can be voted for this proposal: *Var A:* Integrate the proposed Skin improvements and the new ColorTheme into platform Demo at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WebHome *Var B: *Don't integrate anything in the 3.4 timeframe and wait for a new complete skin in 4.x = Current skin + default ColorTheme (no changes) Demo at http://incubator.myxwiki.org/xwiki/bin/view/Drafts/WebHome *Var C:* Integrate just the new proposed ColorTheme that will replace the current DefaultColorTheme Demo at http://incubator.myxwiki.org/xwiki/bin/view/Standards/WebHome *Important remarks when making a decision:* *Var B* and *Var C *does not involve any changes, problems or advantages from the current Colibri skin. Advantages for *Var A*: - Tested on IE7, IE8, IE9, Opera 11, Chrome 16, Firefox 8, Safari 5 and works beautifully. - Uses CSS3 declarations that makes the skin more nice (gradients, round corners, shades, etc.) Problems for *Var A*: - The existing ColorThemes (from the ColorThemes space and extensions.xwiki.org) will become deprecated for XE 3.4 since the new skin needs shades for the gradients (this means the existing ColorThemes variables will be either used in ways they were not intended or they will not have all the variables declared). See my previous mail about "[Discussion] Problematic ColorTheme extensibility"<http://xwiki.markmail.org/thread/ex6fgou6fl6vjwfr> - The CSS will become even more invalid (right now we have a -moz-border-radius and a word-wrap non valid declarations), but the new code contains 154 declarations for the gradients (covering -moz-linear-gradient, -webkit-gradient, -webkit-linear-gradient, -o-linear-gradient, -ms-linear-gradient, linear-gradient and filter: progid:DXImageTransform.Microsoft.gradient proprietary declarations). The invalidity comes because the proprietary declarations are not yet W3C standard (and will not ever be a standard). The proposed standard W3C declaration (linear-gradient) is not yet supported consistently and correctly by browsers, but when it will become standard we can remove all the other proprietary declarations. Please cast your vote. Thanks, Caty