summaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2007-12-12 17:14:10 -0500
committerJoey Hess <joey@kitenet.net>2007-12-12 17:14:10 -0500
commitaa2e20cb127be5c2d245cf44c4b579e7e17e503d (patch)
tree91bc761baa8309ba01bcf6c48593cf48c9e9f5ea /doc/bugs
parent610e67199ce4d5c26327cd129d93ba4975cde664 (diff)
response
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/__96____96__clear:_both__39____39___for___96__.page__42____39____63__.mdwn7
1 files changed, 7 insertions, 0 deletions
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..e389ce3ed 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,10 @@ 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]]