Closed
Bug 211969
Opened 22 years ago
Closed 22 years ago
Text with · and superscripts is very badly layed out.
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jaapsch, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Lines containing · and a superscript causes bad layout
problems in Mozilla, making text seem to dissappear completely when you
change the width of the window. This is especially annoying if you
want to write a number in scientific notation, for example 2·10<sup>6</sup>.
This occurs in Mozilla 1.4 and 1.3, but not in 1.2. What happens is that
the document becomes ridiculously long - selecting all the text (e.g. press
ctrl-a) is revealing. It seems that some of the text height has become huge.
Could this be caused by an unsigned integer underflow?
Note that the effect always happens consistently if the offending
text is not enclosed in <p> tags.
It happens regardless of mode (standard, quirk).
See
http://www.geocities.com/jaapsch/mozbug.htm
for an example of the problem.
Reproducible: Always
Steps to Reproduce:
See
http://www.geocities.com/jaapsch/mozbug.htm
Then slowly change width of window.
Actual Results:
Not only will the final paragraph be pushed extremely far offscreen (excusable
due to 'bad' html), but at some widths, the middle paragraphs also dissappear
offscreen in the same way (even on pages that are fully compliant).
Does this work in current trunk builds? This could be a duplicate of bug 113779.
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
The paragraphs around it move slightly when lines start to wrap, but it all
looks normal.
Thanks guys. I had overlooked bug 113779 (it had no mention of superscript).
I just downloaded and installed the nightly build. It seems the bug has indeed
been fixed, as it now behaves as it should.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•