Closed Bug 2873 Opened 26 years ago Closed 26 years ago

[PP] Italic text displays double-spaced chars for HTML tags

Categories

(MozillaClassic Graveyard :: Composer, defect, P1)

PowerPC
All

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: gerardok, Assigned: buster)

Details

(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #329116 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=329116 Imported into Bugzilla on 02/03/99 18:05) [Export build] Characters are double spaced wherever an HTML tag is found inside <i> and </i> tags. It happens only on Mac. Steps to reproduce: 1. Create an HTML file with the following content: <HTML> <HEAD> <TITLE>test</TITLE> </HEAD> <BODY> <I>fo<B>o</B>o<FONT COLOR="#3333FF">o</FONT>oo</I> </BODY> </HTML> 2. Display file in Navigator /* Notice spacing aroung bold "o" and blue "o" */ It's not a regression from previous releases.
Would not hold 4.5 for this. Is there a workaround?
Moving to 5.0 This aint a regression.
Gerardo--could you compare this behavior to that of "SimpleText" or "TeachText" or other notepad-like software on the Macintosh? Thanks!
Kathy - the described issue can't be compared to that of a text editor because it's all about how HTML tags interfere to the layout of italic text. The same fault causes some Composer plugins to fail on italic text (i.e. an space would be displayed for each HTML tag inserted by Colorize on italic text) It happens in 4.5 only, no failure in Gromit 10/8.
OS: All
QA Contact: 4015
beppe, please assign to appropriate QA Contact for regression across all platforms with latest build.
Assignee: dp → kipp
Summary: Italic text displays double-spaced chars for HTML tags → [PP] Italic text displays double-spaced chars for HTML tags
Setting to [PP] since only on the Mac
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
This failure doesn't apply to Seamonkey. Marking as invalid.
Status: RESOLVED → VERIFIED
Verified on 1/28 build for Mac.
Target Milestone: M3
You need to log in before you can comment on or make changes to this bug.