User talk:Ague

CSS definition order

 * I created a test environment and did some testing of the css extension.
 * It seems that the styles injected on the page ( either at the element level or with the css extension ) can not be overwritten by and user means ( User:common.css or User:common.js ).
 * Are you aware of any method that can be used to isolate css attributes to their respective pages, but still allow users to customize the appearance?
 * Check out CSS test page, attributes defined on page do not get overwritten by what i've defined in User:Joenuts/common.css. Remove inline attributes and what was defined in joenuts/common.css takes over. Remove what was defined in Joenuts/common.css and mediawiki:common.css takes over.
 * Joenuts (Contributions • Message) 14:56, January 29, 2014 (EST)


 * First thing I would do is (temporarily, for testing purposes) change the class names on your test site. the common.css files are likely overwriting the css tags for whatever reason.  remember, the purpose of the css tags is to inject css into the head of the document where it's acceptable to define classes.  once you do that, you will be able to have a level testing ground.  let me know how it goes.  Ague (Contributions • &uArr; top &uArr;) 15:48, January 29, 2014 (EST)