[KULRICE-7469] UI Framework - CSS class hierarchy - support for multiple themes -cleanup Created: 11/Jun/12 Updated: 21/May/15 Resolved: 29/Jul/14
|Project:||Kuali Rice Development|
|Component/s:||Development, User Experience (UX), User Interface|
|Fix Version/s:||Not version specific|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||William Washington (Inactive)||Assignee:||Tom Clark|
|Σ Remaining Estimate:||Not Specified||Remaining Estimate:||Not Specified|
|Σ Time Spent:||Not Specified||Time Spent:||Not Specified|
|Σ Original Estimate:||Not Specified||Original Estimate:||Not Specified|
|Attachments:||KNS L&F in 2.0 vs 2.2 M1 - example1.pdf|
|Epic Link:||UI Theme|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
1) Styles should be defined in the theme "branches", not in the bean/class' parent/base "root" that then applies across all themes. KRAD support for themes (and supply of at least 2 that applications can choose from/inherit) is important, demonstrating how easy it is for applications and institutions to customize through KRAD.
For example, in 2.2, the KNS L&F has inherited various font and other visual treatments from the KS L&F specs, whereas in 2.0, these were at the theme level (respecting the KNS L&F choices). These should be corrected to use the KNS L&F or the KS L&F, as appropriate, depending on the selected theme.
2) Both themes should use px for margins and padding, but not for fonts (use ems or % for fonts). There are several elements that have been changed in 2.2 to use px for fonts. These should be corrected (for example, in all headings for both themes).
3) Both themes should include a fall-back list of font families for every element (there should be no element that lists only one font family. For example, list "Helvetica, Arial, sans-serif" or "Times New Roman, Georgia, serif" instead of "Helvetica" or "Times New Roman". Without a fall-back list, there can be problems with font size inheritance when people use some methods to enlarge font sizing.
See attachment for example where we have only one font defined for H2s in the portal, whereas all the other UI text elements include a fall-back list.
|Comment by Jessica Coltrin (Inactive) [ 16/Oct/12 ]|
moving non-blocker and non-critical m4 Jiras to 2.2-backlog
|Comment by Tom Clark [ 29/Jul/14 ]|
resolving this, based on completion of subtasks