X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/d86cd924b36ed5625c900bd7bba818c9f91e11be..56d32804dd6a0bd46e74ae570070b98e74578058:/doc/todo/concatenating_or_compiling_CSS.mdwn

diff --git a/doc/todo/concatenating_or_compiling_CSS.mdwn b/doc/todo/concatenating_or_compiling_CSS.mdwn
index b9c6234ee..068be9398 100644
--- a/doc/todo/concatenating_or_compiling_CSS.mdwn
+++ b/doc/todo/concatenating_or_compiling_CSS.mdwn
@@ -133,7 +133,7 @@ this without that feature initially.
 >> CSS files can be marked "to be cached forever" (which can be done if
 >> they have content-based filenames).
 >>
->> In terms of time, [[!wp HTTP_pipelining desc="according to Wikipedia"]]
+>> In terms of time, [[!wikipedia HTTP_pipelining desc="according to Wikipedia"]]
 >> browsers don't generally pipeline requests, so the page won't finish
 >> loading until one round-trip time per uncached CSS file has elapsed.
 >>
@@ -151,3 +151,9 @@ this without that feature initially.
 >> think that's the case (apart from possibly local.css, which is why
 >> I'm not sure whether to include it in this).
 >> --smcv
+
+>>> I must admit that I am not aware of how those several CSS inclusion lines
+>>> tend to make browsing less smooth. Please withdraw my comment.
+>>>
+>>> As you pointed out, CSS inclusion is more painful than it should be, and
+>>> your proposal seems to answer that. Go ahead! --[[Louis|spalax]]