161250 - whitespaces negative in front of links or italic text

Status: RESOLVED FIXED

(Core :: Layout, defect, P3)

Description

[Dieter Siebörger]

Some of the white spaces in front of links or italic text became negative: one
character over each other

Comment 1

[Kai Lahmann (is there, where MNG is)]

WFM, Linux, 2002080508

which build are you using?

Comment 2

[Dieter Siebörger]

Build 2002080508

Comment 3

[Matthias Versen [:Matti]]

wfm with win2k build 20020803..

Comment 4

[Jo Hermans]

Worksforme on Mac OS 9, build 2002080508 (same version as you).

Comment 5

[Greg K.]

WorksForMe using Mac/2002080208/9.2.2. Dieter, please attach a screenshot.

Comment 6

[Dieter Siebörger]

Attachment: Screenshot showing negative spaces

The negative spaces depends on fonts settings. When I found the problem, I used
font settings proportional: serif 13 serif: times. Text Zoom 100%
With size 8;12;24 (all factors of my disply resolution 96dpi) there are no
negative spaces although the size of the white spaces IMHO is sometimes a
little wrong. 
With text zoom 120% the expected 10point size shows good text.
E.G use http://www.heise.de/newsticker/data/jk-03.08.02-000/ because it uses so
much links.
With other fonts like Times New Roman I did not see negative spaces although
the  spacing was not correct.

Comment 7

[Greg K.]

Confirmed using Mac/2002080208/9.2.2, using the font settings in comment 6. Reassigning to 
Layout.

Comment 8

[[e-mail]]

wfm build 2002081018 winxp with settings of comment 6

Comment 9

[Frankie]

Attachment: screwy spacing in italics, changes with selection

This may or may not be the same bug. It has similar conditions (Mac Mozilla,
italic text) but different behavior (positive whitespace substituted for
non-alpha characters, notably single quote, which changes in response to text
selection).

The enclosed animated gif should illustrate it fairly well.

Comment 10

[Frankie]

My italic whitespace problem seems to have gone away. How about you Dieter?

Comment 11

[Dieter Siebörger]

Yes, Frankie, I don't see it any more. Seems to be fixed in 1.2 final (maybe
earlier)