aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-08-04 15:08:27 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-08-04 15:08:27 -0400
commitd1cb73cb55ce2ecf185e2554a878a689113a01e4 (patch)
treea8a3cbf15ff99c1a66a7760b7efa29ebf42e8742 /doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn
parent6e2f9e97f3eb2e8e7ecdc2bdcf053a1323df4af8 (diff)
downloadikiwiki-d1cb73cb55ce2ecf185e2554a878a689113a01e4.tar
ikiwiki-d1cb73cb55ce2ecf185e2554a878a689113a01e4.tar.gz
set background color of floating divs
If a floating div is next to (and in front of) a div that takes up the whole screen width, and has a background color set, that color can bleed through into the floating div. One exampe of this is inline's blogpost form. Avoid it by setting the background color of the floating element.
Diffstat (limited to 'doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn')
-rw-r--r--doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn b/doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn
index 90bb800a5..140669ea1 100644
--- a/doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn
+++ b/doc/bugs/sidebar_is_obscured_by_recentchanges.mdwn
@@ -9,6 +9,14 @@ For example, my wiki's [front](http://www.cse.unsw.edu.au/~cs3431/wiki/) and [ne
to <code>local.css</code> to get the border and make sure that the RSS feed's grey title didn't show through on the news page.)
+> Hmm the background color setting seems like a change it makes sense to make to
+> style.css .. done.
+> --[[Joey]]
+
Unfortunately, the [recentchanges](http://www.cse.unsw.edu.au/~cs3431/wiki/recentchanges/) page doesn't look so nice - the sidebar appears below the recentchanges list.
I don't understand why the sidebar is appearing below the recentchanges inline, but above the news inline.
+
+> I don't see the problem here in firefox 3. The sidebar is at the top of
+> both pages. However, it might have to do with the recentchanges page
+> itself using floating elements to build up the table-like display. --[[Joey]]