• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

There are two skins shipped by default, Classic and Pattern, but only one available set of pointer to CSS files (TWIKILAYOUTURL etc). This means that there is no simple way to have a different CSS for different skins.

Example of where this is a problem; in edit.kupu.tmpl I include the CSS files using

   @import url("%TWIKILAYOUTURL%");
   @import url("%TWIKISTYLEURL%");
   @import url("%USERLAYOUTURL%");
   @import url("%USERSTYLEURL%");
which gives the Wysiwyg editor a "pattern" look and feel. This is fine when the editor is invoked from Pattern skin, but when it is is invoked from Classic skin i would like it to pick up the look and feel from there instead.



Undeferred, post Dakar CC
But TWIKILAYOUTURL etc is pattern skin only. So when you have your skin set to Classic the variables are not used (they should not) - css.classic.tmpl does not use the variables.


Summary TWikiPreferences for CSS mixes up skin styles
ReportedBy CrawfordCurrie

SVN Range Sat, 14 Jan 2006 build 8289
AppliesTo Extension
Component PatternSkin
Priority Normal
CurrentState No Action Required


TargetRelease major
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r6 - 2006-04-02 - ArthurClemens
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback