X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/aebd98f62e3fd3132dc854ba1389121d7ca61e2c..19ff6180a8bbb2e5441fe177a934e146d129f1c7:/doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn diff --git a/doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn b/doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn index 1f3c9bbb6..a1b5ba94a 100644 --- a/doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn +++ b/doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn @@ -8,3 +8,28 @@ for `.pagedate, .pagelicense, .pagecopyright`. I can override this in `local.css`, but what was the original reason for adding this `clear: both`? + +> Without investigating in detail, I think it was probably because any +> of the items can be enabled or disabled. So any of them might be the +> first item after the horizontal rule, and any might be the last item +> before the modification date. So all of them have to clear both above and +> below. I'm sure there are better ways for the CSS to handle that. +> --[[Joey]] + +>> There is indeed a better way - all the optional things below the +>> content are wrapped in `