Closed Bug 292663 Opened 20 years ago Closed 19 years ago

Missing matching </FONT> or </P> tags messes up monospace

Categories

(Core :: DOM: HTML Parser, defect)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: mr_walsh, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Take this example, which works.
<html>
<FONT size=3 FACE="sans-serif, Arial, Helvetica, Geneva"> 

proportional<BR> spacing<BR>
<PRE>
mono
space
</PRE>
<p></p>
</FONT>
</body>
</html>

But then eliminate *either* the </PRE> or </P> tag.  Firefox will then
incorrectly render the mono space portion as simply a smaller font.  Yes, this
is imperfect <HTML> but it should tolerate it.  Works on IE.

Reproducible: Always

Steps to Reproduce:
1. Take the sample program in my 'details'
2. View as-is - looks normal
3. Eliminate the </FONT> and or </P> tag.

Actual Results:  
Monospace text is then rendered incorrectly as proportional text.

Expected Results:  
It should tolerate the missing tag matches and render it as expected as monospace.
-> parser, I guess
Assignee: nobody → parser
Component: Layout: Fonts and Text → HTML: Parser
QA Contact: layout.fonts-and-text → mrbkap
The inconsistancy you're seeing is because when we can say for sure that the
code is "well formed" (i.e., well nested) we don't activate residual style
handling. When you remove one of the end tags, then we activate residual style
handling. So we're getting a DOM that looks like <font></font><pre><font> so the
font overrides the pre's font. This *might* end up being WONTFIX, but it
deserves another look (since I can think of a couple of potential solutions).
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.