Closed
Bug 64878
Opened 25 years ago
Closed 25 years ago
Rendering of 0.7 Gecko much worse than 0.6 Gecko!! Site included!
Categories
(Core :: Layout: Tables, defect)
Tracking
()
People
(Reporter: martin, Assigned: karnaze)
References
()
Details
(Keywords: compat)
Attachments
(4 files)
Please check this site! Mozillas rendering disimproved since version 0.6 (which
was pretty much ok). Click on the UK-flag in the lower left corner, then click
on "Try Out" and "Try now". You will get to the search screen. In the lower left
frame the site shows a tree view. This is (almost) PLAIN HTML 3.2. The only
speciality I can think of is the background image for table datas. Compare with
Netscape 4.6 or IE > 4.0 !! Mozilla's 0.7 rendering is broken, at least for this
HTML.
Besides from the site above, I already enjoy surfing the Web with Mozilla (0.6).
Keep up the good work guys.
If your are interested I have some site's programmed up with much more
sophisticated HTML than www.xxp.de has.
Martin
Comment 1•25 years ago
|
||
IMHO the rendering seemed Identical in both versions. The text also looked the
same - foreign :)
Comment 2•25 years ago
|
||
I checked the Tryout Now (I missed that before), and what I found was that the
rendering was identical. I don't exactly see what the problem is.
Comment 3•25 years ago
|
||
BTW - you might want to look at the bug-reporting guidelines:
http://www.mozilla.org/quality/bug-writing-guidelines.html
Sorry about the spam.
Updated•25 years ago
|
Comment 4•25 years ago
|
||
The offending frame is full of document.all / document.layer stuff, which is
not W3C-compliant, and which we do not support.
->Evang
Comment 5•25 years ago
|
||
I don't know what you guys are seeing, but I can't reproduce neither the
layer/all thing, nor can I see any difference with 4.7.
Reporter, could you please provide a more precise description of *where* the
problem is? (for example I don't see a lower left frame, only a left and a right
frame).
Thanks,
Fabian.
i think i'm seeing this problem. i've attached screenshot of my Linux 20010108
nightly build, look at the left frame. there is indentation problem with
tree-like menu. in NC4.7 this menu looks good. layout?
Comment 8•25 years ago
|
||
Verifying "problem" on Mozilla 0.7 on page http://www.xxp.de/cgi-bin/axp?
SCZ=5218&sessionId=979136301440KUCLYQFYBZA&lg=1&mainLayout=WEB
Comment 9•25 years ago
|
||
You have to expand the menus BTW
Comment 10•25 years ago
|
||
Using build 2001010904 on WinNT4
Did you see what I see? This page never stops loading! If I stop my browser
loading this page, and close/reopen browser window then the problem is gone! So
this might be an incremental reflow error!? B.T.W. there is another bug reported
about the same sort of menu's.
Comment 11•25 years ago
|
||
Comment 12•25 years ago
|
||
Comment 13•25 years ago
|
||
CC:ing
Comment 14•25 years ago
|
||
On the first place, after looking in to 20 files of that site, I did not found a
single document.all. So A: "there is no document.all" B: "This website is
changed" or C: "I'm blind!". Fabian, you also didn't find one, right? And just
to be sure, there are 3 frame's "top" (you know where) "nav"(left frame) and
"inhalt" (right frame). So Fabian is right by saying that he didn't see an lower
left frame! Because there's simple no "lower" left frame!!
Tip for Martin:
Martin can you please take a second look at your frameset documents?! And to be
more precise, the FramesetE.html and FramesetD.html. Ask yourself, is that the
right place to put them into your document?? ==> <noframes>....</noframes> <==
Most friendly, HJ.
Updated•25 years ago
|
Component: Evangelism → HTMLTables
Comment 15•25 years ago
|
||
The problem is in the following markup:
<tr>
<td WIDTH=30></td>
<td WIDTH=10></td>
<td WIDTH=100%></td>
<td WIDTH=10></td>
</tr>
note that the widths add to more than 100% (100% + 50px). Removing the
width="100%" from the <td> and moving it to the <tr> makes the page lay out
correctly in linux build 2001-01-05-08.
Over to HTML Tables for triage.
Comment 16•25 years ago
|
||
Weird: I had a different rendering problem than both of you, and I only had it
after Zeigenspeil or whatever was clicked on and expanded. Putin was not in the
right place.
Win2000 - moz 0.7
No offence, Boris - but I am not convinced that is the problem. I think it
might have to do with </A> appearing with no <A> tags in certain places and the
<A NAME="0"></A> which is improper HTML. Since neither H-J's testcase or my
testcase I tried to make caused any problems in Mozilla, I am really at a loss
here.
Comment 17•25 years ago
|
||
Doh, almost forgot - the reason I am not conviced is because the 100% is in a
seperate table.
Comment 18•25 years ago
|
||
Comment 19•25 years ago
|
||
I changed the table as Boris told, but as you can see in my last screenshot,
that seems of no help to it. After 11 test, this pops up. I think this might be
another problem related to the latest table layout issues. I have seen a lot of
tables with the same markup errors in it, even here on Bugzilla.
Comment 20•25 years ago
|
||
additional comment: every time i reload H-J's testcase, the rendering looks
different, and still broken, like on my screenshot.
Comment 21•25 years ago
|
||
*** Bug 65178 has been marked as a duplicate of this bug. ***
Comment 22•25 years ago
|
||
i think this is a duplicate of bug 63445
Comment 23•25 years ago
|
||
Well if it is the patch didnt fix it (which was checked in yesterday). Any other
ideas?
Comment 24•25 years ago
|
||
tested with buildid 2001011220 on win98(tried several times)
this does not occure anymore due fixed bug 63445
can someone check if it's fixed on linux and mark is as dupe ?
Comment 25•25 years ago
|
||
Yabadabadoo, karnaze must have fixed a lot of problems with that patch!!!!
Tnx man. (confirming fix)
Comment 26•25 years ago
|
||
markin' as duplicate
*** This bug has been marked as a duplicate of 63445 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 27•25 years ago
|
||
Verified dupe of fixed bug 63445: "tables incorrectly widened to 100% width"
(tested with 2001011521 nightly)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•