For example http://packages.gentoo.org/ebuilds/?gentoo-sources-2.6.16-r10 (but all such pages). When changelog is too wide (or browser window too thin) it overlaps the package "box" picture, making it unreadable. I found this in RSS reader Akregator (uses Konqueror for rendering, where it also happens). In Firefox this doesn't happen, but in Opera it does, so it's 2:1 chance it's bug of the page, not browser :) The code goes like: <td valign="top" class="item"> <p> <b>Description:</b> <img align="right" src="http://packages.gentoo.org/images/sys-kernel/gentoo-sources.jpg" alt="" class="pkgimg"/> </p> <p> <b>Changes:</b> <br/> ... I'm not HTML expert but I think this meens the image is aligned right only inside the paragraph, with respect to the <b>Description:</b> which is on the same level. But Changelog is in different paragraph. Also, the page doesn't validate with http://validator.w3.org
OK I found the cause and very simple and easy fix: - <tr><td class="item" valign="top"><p><b>Description:</b> The Portage Package Management System. The primary package management and distribution system for Gentoo. <img class="pkgimg" alt="" src="Gentoo%20Linux%20--%20The%20Fresh%20Ebuilds_files/portage.jpg" align="right"></p><p><b>Changes:</b><br><span style="white-space: pre;">*portage-2.1.2_pre1-r2 (25 Sep 2006) + <tr><td class="item" valign="top"><p><b>Description:</b> The Portage Package Management System. The primary package management and distribution system for Gentoo. <img class="pkgimg" alt="" src="Gentoo%20Linux%20--%20The%20Fresh%20Ebuilds_files/portage.jpg" align="right"></p><p><b>Changes:</b><br><span style="white-space: pre-wrap;">*portage-2.1.2_pre1-r2 (25 Sep 2006) The difference is changing style "white-space: pre;" to "white-space: pre-wrap;" This ensures wrapping is done also when needed by the browser (i.e. to wrap around the image), not just when the text itself contains a newline. Tested and works in firefox, opera and konqueror. Please consider applying it, it's really annoying bug, thanks.
I could not repeat the error, but I did implemented the suggested change. Thanks for reporting this.
Thanks, really fixed the issue in Akregator :)