This is a meta bug for all the open floater bugs.
It has been created because after being more and more annoyed at floats, I have
now reached the point where I'm ready to bring this to the next level.
I will buy lunch for whomever fixes floats so that they work properly.
Not just any lunch, either. A decent meal in any restaurant of your choice, so
long as I'm there to thank you in person.
Does Bug 52916 need to be added to the dependency list?
Ian this bug is wrong assigned ;-), it could be directly assigned to
email@example.com. Most of the bug's are buster's bugs, who left netscape
and his bug's to us. So my guess is, that the ultimate fix depends on the
ability to hire somebody on buster's position. So may be you should invest your
lunch in a business lunch with your boss. :-)
As much as I hat to do it, reassigning to me.
should bug 66796 be added to the list?
--> 1.0 for meta-bug
Alex is looking at floater issues. Reassigning to Alex
Moving to Mozilla1.1. Engineers are overloaded with higher priority bugs.
Not sure if this is the right place, maybe someone can note the correct bug...
This is a bug when the page loads slowly. Floated image screws up. Should be in
the top left corner. Works fine if page loads fast, or offline. Really annoying.
Anyone know a workaround? Or is the code wrong?
(only good for 40 days)
Yes, this is the wrong place to post this.
This is a meta bug to keep track of other bugs, not a place to post new bugs in.
Report new bugs in a new bugthread (however in this specific case I would not
bother, since looking at the page source reveals it's very buggy. Next time
check a page at http://validator.w3.org before posting issues as a bug :) )
batch: adding topembed per Gecko2 document
Bulk adding topembed keyword. Gecko/embedding needed.
removing topembed as this is a meta
I hope you understand my english and I found the right place ;-)
If i use a table with 100% the content in the table overlaps the flaoting image.
The table should be handled as block with line-break a after the imgage.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de" lang="de">
<head><title>Float Problem Imgages</title></head>
<p><img src="schleimmonster.jpg" width="200" height="283" border="0" alt="test"
style="margin-left: 10px; margin-bottom: 1em; float: right" /></p>
<table style="width:100%; border: 1px solid #000">
<td>Tabelle Tabelle Tabelle Tabelle Tabelle Tabelle Tabelle Tabelle Tabelle</td>
> and I found the right place
You didn't. You want bug 14984
Sorry if this is the wrong place...I'm not sure if this is related or if it's a different bug. If you first go to this page to "select" the theme http://demo.jauhari.net/?wptheme=Prosumer then go to this page to see the test post http://demo.jauhari.net/the-power-of-social-media/ you will *not* see the picture in that post. It seems like there's a problem where (at least for that particular Wordpress theme) that if you use a span style float:left;margin-right:10px; to wrap the text around the picture, the picture doesn't even show up in Camino. The page displays correctly in Mac OS X Safari 3.1.2 and Firefox 3.0.5.
Sounds like you should file a Camino bug. I doubt your issue is related to floats....
Sorry, didn't realize bug 78094 wasn't specific to Camino. Will file a Camino bug report instead.