Extension talk:CSS/Archive

Parser-caching problem
There's a bug which is causing the CSS to intermitently not get included in the page and I haven't been able to figure out how to fix it yet. This is why the status of the extension has been returned to "beta". There's an example of this extension in use at CSS example, if the page has big coloured spots in the background, the the css has been included properly.
 * The bug is probably related to parser caching as I didn't see any provision in your code to account for this functionality. Jean-Lou Dupont 23:50, 24 August 2007 (UTC)
 * Thanks a lot! that was the problem :-) --Nad 23:58, 24 August 2007 (UTC)

Produces Invalid HTML
The URLs generated contain ampersands which are not properly escaped, so wiki pages which use this extension are no longer valid XHTML. See the output from the W3C HTML validator on the Spots page On that page there are some other markup errors, but on some sites the only markup errors are due to this extension. This makes CSS.php unusable on sites which care about HTML validity.

Simple to fix. Add this line in magicCss: $url = str_replace("&", "&amp;amp;", $url);

At least, that does it for me. (Note that I had to double the escaping to get this patch to appear on this wiki page.) -- sandro@w3.org 13:53, 29 December 2007
 * Ok thanks, I've added that in --Nad 21:26, 30 December 2007 (UTC)

Doesn't work with Cite extension
There seems to be a bug with this extension when cite.php is also used. The style sheet referenced appears to be ignored. Could anyone point towards how this might be corrected? --Philipjoslin 10:01, 6 December 2007 (UTC)
 * Is the site you have it on public so I can have a look at what's happening? is there errors or anything? --Nad 21:34, 8 December 2007 (UTC)
 * I have Cite and CSS installed and CSS does not work. The Wiki I am using is not public, sorry. --EToreo 20:53, 19 December 2007 (UTC)

Will this work for longer CSS coding?
I have a page that requires CSS in it. The CSS coding is much longer than that shown on the example page. When I created a page called Syn'sTemplateDesignPageCSS.css and inserted the CSS coding, then added the tag to the page to call the CSS, it didn't work. 75.167.200.148 01:02, 5 March 2008 (UTC)

1.12
This doesn't seem to be working in 1.12. --Sasoriza 13:15, 27 March 2008 (UTC)

Has anyone made progress with getting this to work in 1.12? While there are alternatives (like Extension:PageCSS), many pages are already using this extension, which would be time-consuming to change individually (and don't say, use a bot). This extension should be upgraded to work in newer versions if possible. –Sasoriza 13:30, 23 May 2008 (UTC)
 * Try installing the new version on SVN --Zven 23:38, 31 May 2008 (UTC)
 * I have it running on 1.12 with no problems. The extension does not prevent other CSS's such as Common.css or Monobook.css from loading, it simply adds another CSS which is loaded before the main ones which means you will have to ensure that your CSS rules are more specific than the existing ones to prevent them being overridden (this is what I mean by "specific"). Also I've made a few changes to the code to allow files or in-line rules to be included. --Nad 01:40, 1 June 2008 (UTC)

Inline CSS
I've noticed that inline css gets escaped with htmlspecialchars (line 44 current SVN revision). This conflicts with some chars used in CSS like quotes. becomes I don't think this is the desired result ;-) Imo htmlspecialchars should simply be removed. Thanks. Der Papst 20:35, 30 July 2008 (UTC)