from:n.p.m.general Why does the html below render the alignment of these three sets of tables differently? More importantly, though, is that it seems to me that _none_ of them would be what a designer would want to happen (which would be having 'table two' take up all the space that table one hasn't...on the same line...all within the browser window). Mark, Chris, testcase here in table layout.. -dennis possibly blocking 104012 and 102800? or other layout issues?
Am I missing an obvious way to get the desired layout? Regardless, at least one of these layouts below seems like a bug, would y'all agree? dan.
anyway if you diagree if this is a valid bug or not, please let me know.. on first glance this looks to be buggy.. I've done some reading on alignment/table stuff not sure exactly if the output is correct. -Dennis
Keywords: helpwanted, qawanted, testcase
There are 3 cases in this bug.. but I think only the first case is buggy. In the other two cases NS6.2 is rendering correct..
Yeah, first case is buggy. Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: tables are not rendered the same: using different syntax. → tables overlapping due to align: right
just updating: haven't seen anything fix the first table, nor regress the botton two. Still the same in a latest nightly. 2002-3-17-08.
Probably a block floater problem. Reassigning to alexsavulov. If someone can produce a url, we can raise the priority.
Assignee: karnaze → alexsavulov
Component: HTMLTables → Layout
Priority: -- → P3
Target Milestone: mozilla1.2 → Future
*********************** reference to bug 122200 *********************** I know this problem. IE does not deal properly with this too. I did a patch for the align=left problem but I didn't wanted to repair the align=right problem because this would complicate the code a lot. As long as there are no real world pages that use this (and i doubt that since IE does not work too), we won't uselesly complicate the nsBlockReflowState code. Correct me if I'm wrong.
Assignee: alexsavulov → float
Component: Layout → Layout: Floats
QA Contact: amar → ian
I think the only reason that there are no real world examples of this is precisely because of the bugs in both cases. I'd like to add another example of the bug that is present in the attachment above, but not visible due to all of the BR elements he uses. When you build a table with it's width set to 100%, and it's alignment set to 100%, following elements do not respect the table space, and render directly on top of it. IE is broke in the same way. -firstname.lastname@example.org
Created attachment 125889 [details] Test case two... This is the same bug, I believe, but a clearer test case...
In the above comment, I meant width of 100%, and alignment set to right. That's what the new attachment shows... -email@example.com
dup *** This bug has been marked as a duplicate of 14984 ***
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.