Closed
Bug 77282
Opened 24 years ago
Closed 20 years ago
Bad: GUI, or html rendering scewup
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: icecap85, Unassigned)
References
()
Details
Attachments
(9 files)
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (Win98; U)
BuildID: 2001042304
Mozilla cant correctly display html on some sites. Such as yours, the site/page
with html gets squashed up, and screwed up.
Reproducible: Always
Steps to Reproduce:
1. Go to http://www.mozilla.org
2. Move the page up/down/side to side
3. The page looks screwed up.
Actual Results: The page gets screwed up.
Expected Results: For the page not to get screwed up.
Uh, oh yeah java wont work either. I have some screen shots of the problem, if
you want them please respond with a request to my email account:
icecap85@hotmail.com
Comment 1•24 years ago
|
||
screenshots would be good, since I can't produce this "screwup" you speak of.
Linux build 2001-04-23-08.
Reporter | ||
Comment 2•24 years ago
|
||
Reporter | ||
Comment 3•24 years ago
|
||
reporter: what resolution are you running at, and what other interesting
settings do you have? [confirming because I can't recall seeing a report like
this]
Assignee: asa → pavlov
Status: UNCONFIRMED → NEW
Component: Browser-General → ImageLib
Ever confirmed: true
QA Contact: doronr → tpreston
sorry, pavlov suggests layout, but i'm puzzled as to how the M logo got stuck
on the scrollbar
Assignee: pavlov → karnaze
Component: ImageLib → Layout
QA Contact: tpreston → petersen
Comment 6•24 years ago
|
||
Interested, adding myself to CC list
Comment 7•24 years ago
|
||
I could be wrong, but the screwed up pics have the feeling of "low resources" or
something funky in the video driver. Reporter, I'd be curious what your system
resources are when this happens (right-click My Computer, choose Properties, go
to the Performance tab, and see what it reports for System Resources). Also,
you wouldn't happen to be overclocking your video card or anything, would you?
Comment 8•24 years ago
|
||
Email from reporter:
I went to view the bug report page. And it just screwed up some how.
Reporter | ||
Comment 9•24 years ago
|
||
I had 60% of my resources free when it happend.
Comment 10•24 years ago
|
||
More email from reporter:
"Yes well my system resources are above 60% when this happens. I have a rage
turbo pro integrated graphics card, 4mb."
Hmm, 60% is actually low enough to cause problems sometimes, but it's not
conclusive.
Reporter | ||
Comment 11•24 years ago
|
||
Comment 12•24 years ago
|
||
Reporter, the amount of actual RAM probably has nothing to do with it, since
system resources only depends on the GDI and User heaps. My own experience has
been that Windows 9x starts getting flakey when resources get down to the 60% to
65% level, regardless of what application.
Anyway, some other things to try are: lowering your color depth, if you're
running at 32bit color. Also try different versions of ATI's drivers for your
card. ATI doesn't always produce the best drivers, and sometimes they have
funky hacks in them to speed things up. A number of graphics apps, for example,
have specific workarounds for "special" optimizations in ATI display drivers.
Reporter | ||
Comment 13•24 years ago
|
||
My system has worked flawless with only 6% of its resources free. When windows
gets low on resources all it does is tell me and it wont let me run any more
programs until the resources free up. So I dont think thats the problem. I never
had this problem with any other browser except mozilla. Thats including Netscape
6.0.
Reporter | ||
Comment 14•24 years ago
|
||
Oh and I am on a 16bit color depth.
Reporter | ||
Comment 15•24 years ago
|
||
Reporter | ||
Updated•24 years ago
|
Priority: -- → P3
Comment 16•24 years ago
|
||
Comment 17•24 years ago
|
||
Comment 18•24 years ago
|
||
Mozilla does not render the following code also:
<DIV class=Section1> <P class=MsoNormal
style="mso-list: none; mso-list-ins: '' 19991102T2025">
</P>
<TABLE border=1 cellPadding=0
style="BORDER-BOTTOM: 4.5pt outset; BORDER-LEFT: 4.5pt outset; BORDER-RIGHT:
4.5pt outset; BORDER-TOP: 4.5pt outset; WIDTH: 100%; mso-cellspacing: 1.5pt"
width="100%">
<TBODY> <TR> <TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="22%"> <P class=MsoNormal><B>Problem Report</B></P>
</TD>
<TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="78%"> <P class=MsoNormal>The system detected an
<B>Unresolved Host Name</B> while attempting to retrieve the URL:
<B>http://source.mozilla.org/</B>.</P>
</TD>
</TR>
<tr> <td
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="22%"> <p class=MsoNormal><b>Message ID</b></p>
</td>
<td
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="78%"> <p class=MsoNormal>UNRESOLVED_HOSTNAME </p>
</td>
</tr>
<TR> <TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="22%"> <P class=MsoNormal><B>Problem Description</B></P>
</TD>
<TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="78%"> <P class=MsoNormal>DNS resolution failure
encountered for the host
'source.mozilla.org'.</P>
</TD>
</TR>
<TR> <TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="22%"> <P class=MsoNormal><B>Possible Problem Cause</B></P>
</TD>
<TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="78%"> <P class=MsoNormal>The host entered has a
mistake or made a mistake, or
the requested Web site is temporarily unavailable in DNS.</P>
</TD>
</TR>
<TR> <TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="22%"> <P class=MsoNormal><B>Possible Solution</B></P>
</TD>
<TD
style="PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-RIGHT: 0.75pt;
PADDING-TOP: 0.75pt" width="78%"> <P class=MsoNormal>Examine or correct any
mistakes, or try again at a
later time.</P>
</TD>
</TR>
</TBODY> </TABLE>
<P> </P>
Comment 19•24 years ago
|
||
Comment 20•24 years ago
|
||
Build ID 2001062815 M 0.9.2 Displays 39378 when it is a file. This is an error
generated by the DNS server when an unresolvable url is passed to Mozilla.
mozilla does not render the code when it is generated, I cannot figure why?
Reporter | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 21•23 years ago
|
||
Reporter | ||
Comment 22•23 years ago
|
||
Comment 23•23 years ago
|
||
*** Bug 101634 has been marked as a duplicate of this bug. ***
Comment 24•23 years ago
|
||
*** Bug 111763 has been marked as a duplicate of this bug. ***
Comment 25•23 years ago
|
||
Reporter of dup bug 101634 uses an ATI rage pro turbo 2x built in on mobo
Reporter of dup bug 111763 uses an ATI Rage Pro AGP 2X
Comment 26•23 years ago
|
||
Temporarily moving to future until a milestone can be assigned.
Target Milestone: --- → Future
Comment 27•23 years ago
|
||
I had this exact problem (and also occasionally saw it in IE). It's an ATI
driver problem, fixed by upgrading my graphics driver (download from ATI
website, IIRC), and possibly DirectX too.
Caveat: the newer version of DirectX broke windows, and I couldn't un-install it
(thanks MS!). I fixed that by installing another "new" ATI graphics driver,
which was labelled as experimental.
Comment 28•22 years ago
|
||
mass reassign to default owner
Assignee: karnaze → table
Status: ASSIGNED → NEW
Component: Layout → Layout: Tables
QA Contact: petersen → madhur
Target Milestone: Future → ---
Updated•22 years ago
|
Target Milestone: --- → Future
Comment 29•22 years ago
|
||
Reporter: are you still experiencing this bug? Have you updated your ATI driver(s)?
Comment 30•20 years ago
|
||
marking as wfm due to a lack of response. Please reopen the bug if the problem
still exists and report if you updated your ATI drivers.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•