Page History
...
Property: | xmlui.theme.mirage.item-list.emphasis |
Example Value: | xmlui.theme.mirage.item-list.emphasis = metadata |
Informational Note: | Determines which style should be used to display item lists. Allowed values:
|
Property: | xmlui.theme.enableConcatenation |
Example Value: | xmlui.theme.enableConcatenation = false |
Informational Note: | Allows to enable concatenation for .js and .css files. Enhances performance when enabled by lowering the number of files that needs to be sent to the client per page request (as mutiple multiple files will be concatenated together and sent as one file). Value can be true or false. False by default. |
Property: | xmlui.theme.enableMinification |
Example Value: | xmlui.theme.enableMinification = false |
Informational Note: | Allows to enable minification for .js and .css files. Enhances performance when enabled by removing unnecessary whitespaces and other characters, thus reducing the size of files to be sent. Value can be true or false. False by default. |
...
- Based on the new restructured dri2xhtml base templates. Templates in the theme, overriding the new base templates, are located in the same folder hierarchy to ensure full transparancytransparency.
- Automated browser feature detection for improved browser compatibility.
- In other themes, user agent detection is used to identify which browser version your user is using. Based on the result of this detection, the theme would use a different cascaded style sheet (CSS) to render a compatible page for the visitor. This approach has 2 major issues:
- User agent detection isn't very reliable
- Maintaining these different CSS files is a maintenance nightmare for developers, especially when using features from newer browsers.
- Mirage applies two novel techniques to resolve these issues
- For compatibility with older Internet Explorer browsers, conditional comments give the body tag a class corresponding to the version of IE
- modernizr is used to detect which css features are available in the user's browser. This way you can target all browsers that support a certain feature using css classes, and rules affecting the same element can be put together in the same place for all browsers.
- In other themes, user agent detection is used to identify which browser version your user is using. Based on the result of this detection, the theme would use a different cascaded style sheet (CSS) to render a compatible page for the visitor. This approach has 2 major issues:
- CSS files are now split up according to function instead of browser. style.css will now fit most needs for customization. Following additional CSS files are included, but will rarely need to be changed:
- reset.css ensures that browser-specific initializations are being reset.
- base.css contains a few base styles
- helper.css contains helper classes to deal with specific functionality.
- handheld.css and print.css enable you to define styles for handheld devices and printing of pages.
- jQuery and jQueryUI are included by default. To avoid conflicts the authority control javascript has been rewritten to use jQuery instead of Prototype and Script.aculo.us.
...
Thanks Peter Dietz for providing this fix. Note: This issue is resolved in 1.7.1
Overview
Content Tools