GNOME Bugzilla – Bug 370990
Too much space after list items containing links
Last modified: 2008-07-15 16:42:37 UTC
See http://live.gnome.org/CVSRepository for an example. The spacing in the list looks wrong, and it's each item that contains a link that has too much margin or padding below it.
This is a parser problem rather than CSS: List elements that contain a link produce a P inside the LI; the others don't.
This annoys me. Is the wiki source/config in SVN somewhere so I can poke at it?
Please take the time and try to identify the bug here: http://moinmo.in/MoinMoinBugs And if you think it doesnt exist create a new issue. You could also test if it still exists here: http://moinmo.in/WikiSandBox MoinMoin 1.6 will be released soon. I dont think it makes sense to start hacking the code in the local version. If there is an accepted patch, maybe, but if not we might not be able to patch in the future. Anybody who wants can download and install a MoinMoin and look at the code: http://moinmo.in/
The problem doesn't exist in http://moinmo.in/WikiSandBox, but I can't find it in the bugs list. I guess I'll survive until 1.6 comes out. :)
So this is not fixed in 1.6, and is seemingly on purpose. The offending code is in MoinMoin/parser/text_moin_wiki.py. For some reason, it imagines that it needs to add extra paragraphs in various situations, which are conveniently identified by obscure meaningless numbers. There are the "line862" paragraphs, the "line867" paragraphs,the "line874" paragraphs, and the ever-popular "line891" paragraphs. (These are the names that get assigned to the CSS class of the paragraphs in question. Since they appear in that order in text_moin_wiki.py, a handful of lines apart each, I'm guessing that the numbers used to refer to line numbers of that source file, though they don't any longer.) Anyway, it turns out that the reason http://moinmo.in/ *appears* to not have the same problem live.gnome.org does is that they added a CSS rule to effectively undo it: li p { margin: 0 } (Yay Firebug, Boo MoinMoin) "display: inline" would probably be a better rule if we want to copy this. Which we do. :)
Ok, if you want to hack on MoinMoin to find the issue: http://moinmo.in/MoinDev/MercurialGuide Did you add a bug in MoinMoin also? If not that would be good, so we can track it. Your help is appreciated.
fixed in 1.6. no further comments from reporter.
Um, this is NOT fixed in 1.6, as described in comment #5. The current best "fix" is to add: li p { margin: 0 } to our css, just like http://moinmo.in/ does
> So this is not fixed in 1.6, and is seemingly on purpose. I can't think of why you'd want to do that. Reopening in light of comment #8