338843 - Changing SVG text in JavaScript artifacts

Status: RESOLVED WORKSFORME

(Core :: SVG, defect)

Description

[Pete Kirkham]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3

When changing SVG text position and content from JavaScript, pixels around the edges of the text which should be refreshed aren't, and pixels are lost from the edge of the text, degrading its appearance. Legibility of small fonts greatly reduced.

Reproducible: Sometimes

Steps to Reproduce:
1. Create a text element, then from javascript change both its text content and position.

Actual Results:  
Some pixels (typically coloured so part of antialiasing) around the previous text location's edges are left behind, some pixels at the edge of the text at the new position are not drawn.

Expected Results:  
The new text should be drawn correctly at the new postition without leaving pixels behind.

Comment 1

[Ryan Jones-Ward [:sciguyryan]]

Attachment: Testcase from OP's URL.

Comment 2

[Robert Longson [:longsonr]]

WFM using a trunk build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060517 Minefield/3.0a1 

I do see the O cut off but not the trail when running in 1.5.0.3 though

Comment 3

[Pete Kirkham]

The trail appears using ClearType font smoothing, is absent with Standard smoothing or no smoothing.

Comment 4

[(not currently active) Ted Mielczarek]

I can reproduce this on WinXP.  I have ClearType enabled, I get exactly the same result as the reporter.

Comment 5

[Jonathan Watt [:jwatt]]

I see this with a lot of the fonts installed on my machine, but not with Verdana.

Comment 6

[Jonathan Watt [:jwatt]]

That was using Firefox 2.0 beta 2. Like Robert, on trunk everything seems to work perfectly, so this is probably WONTFIX since we're way to late for a FF2.0 fix.

Comment 7

[Wayne Mery (:wsmwk)]

Ted, (or anyone) - is/was clearly :) related to cleartype?

Comment 8

[Jonathan Watt [:jwatt]]

Using Firefox 2 I see this bug with and without ClearType turned on. Using current trunk builds, I do not see this bug. Closing as worksforme.