Closed
Bug 463981
Opened 17 years ago
Closed 17 years ago
Text in SVG is grainy
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 311534
People
(Reporter: will.pittenger1+mozbugzilla, Unassigned)
Details
(Keywords: testcase)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
I am testing with Firefox 3.0.3. I can't see anything special about the text other than the size: 16. It would have a clone behind it, but Bug 463980 is probably causing that to be hidden. The text in question is "Douglas city limits".
Three files are attached. The SVG is the problem file. (Same file as Bug 463980.) The first PNG is how Inkscape renders it and what we should see in Firefox. The second PNG is how Firefox 3.0.3 renders it.
Reproducible: Always
Steps to Reproduce:
1. Examine the test case SVG with Firefox 3.0.3.
2. Look at the words "Douglas city limits". You will find that object just above the words "Quarter Bridge Rd".
3. The text in question will be hard to read because of the graininess.
Actual Results:
The text "Douglas city limits" will be hard to read because of the graininess.
Expected Results:
I would expect the text "Douglas city limits" to be easy to read and smooth.
| Reporter | ||
Comment 1•17 years ago
|
||
Examine the text "Douglas city limits" (just above "Quarter Bridge Rd"). It will be hard to read because of the graininess.
| Reporter | ||
Comment 2•17 years ago
|
||
This is the text as rendered by Inkscape.
| Reporter | ||
Comment 3•17 years ago
|
||
This is what Firefox 3.0.3 shows me.
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 5•17 years ago
|
||
(In reply to comment #4)
>
> *** This bug has been marked as a duplicate of bug 311534 ***
Uh, the comments in bug 311534 say it was fixed by a 3.0 beta. I saw it in 3.0.3 release.
Comment 6•17 years ago
|
||
I'm pretty sure 3.0 beta had no changes that would have fixed that bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•