Closed
Bug 22670
Opened 25 years ago
Closed 25 years ago
<FONT SIZE="-1"> does not span <P> </P> tags
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M13
People
(Reporter: pajohnson, Assigned: rickg)
References
()
Details
The web page www.thecanterburyschool.org/Admissions/admissions.htm was generate by NetObject Fusion 3.0 and contains a font size tag that spans multiple paragraphs. Netscape Communicator 4.6 and Internet Explorer 4.5 on the Macintosh render all of the paragraphs up to the </FONT> tag as a smaller font. Mozilla R12 on a Macintosh running OS9 only renders the first paragraph as a smaller font. All paragraphs after the first </P> tag are rendered as normal size.
Comment 2•25 years ago
|
||
This also does not work correctly on WinNT on a recent M13 build, but there seems to be a complication that the fix for 991 may not have contemplated: the first and last <P> elements meant to be spanned by the <FONT SIZE="-1"> element are not completely nested within it. Here's some abstracted HTML based on the frame at http://www.thecanterburyschool.org/Admissions/body_admissions.htm : <P><FONT SIZE="-1">text</P> <P>text</P> ... <P>text</P> <P>text</FONT> <FONT SIZE="-2">text</FONT> <FONT SIZE="-1">text</P> <P>text</FONT> It seems that NetObjects Fusion doesn't bother to nest elements properly. Ouch. Based on what was seen in bug 22711, "Fonts that should be Arial come up Times", the fix for bug 991 wasn't enabled by default in M12, but is in current M13 builds, and works when the <FONT> element completely surrounds multiple <P> elements. Tested with: 1999-12-28-08-M13 nightly binary on Windows NT 4.0sp3
This is fixed in my tree, awaiting an opportune time to land.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 5•25 years ago
|
||
With the Jan 05 build, this problem has been fixed.
SPAM. HTML Element component deprecated, changing component to Layout. See bug 88132 for details.
Component: HTML Element → Layout
You need to log in
before you can comment on or make changes to this bug.
Description
•