Closed
Bug 486832
Opened 16 years ago
Closed 16 years ago
glyphs and svg fonts dont match
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 119490
People
(Reporter: jay, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
(deleted),
image/tiff
|
Details |
open the uri
compare with:
http://www.w3.org/Graphics/SVG/Test/20011026/fonts-fontElement-BE-01.png
parity opera safari
the area to the right of:
SVG over Glyphs
&
Glyphs over SVG
should be a solid black
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•16 years ago
|
||
Reporter | ||
Comment 3•16 years ago
|
||
#1 Robert,
how is this a dupe of bug 119490?
the summary and description are barely similar.
Comment 4•16 years ago
|
||
That bug says we don't do SVG Fonts and this bug says that SVG fonts don't display correctly. Well of course they don't because we don't do them.
Comment 5•16 years ago
|
||
I can see where some of your confusion here arises from. The original reporter in bug 119490 reported 2 issues in one bug instead of filing 2 separate bugs as they should have.
The original summary talks was "Need to support SVG fonts in SVG graphics" yet the initial description in comment 0 talks about a further issue where if you try to use SVG fonts, none of the SVG content displays.
In general, for the Moxzilla project, we try to make as few changes are necessary to the summary and leave rather file separate bugs for issue brought up in comments.
Therefore bug 119490 is about implementing SVG fonts and not about the issue with SVG content not displaying if SVG fonts are used.
At some point it was decided that whatever was done to implement SVG fonts should be more general so that they were not limited in use to SVG graphics contexts.
At that point the Summary was generalized to "Implement SVG fonts".
That is the only bug morphing that took place. We also generally use the term morphing the bug to mean editing the summary to the point where it now longer is describing the same issue the original summary did.
Anyway, in my opinion, this is a duplicate bug and you other bug is really a dependent bug. I adjusted the other bug as such already.
Comment 6•16 years ago
|
||
I meant to mention, but I forgot, that at this point, the bare minimum requirements for marking bug 119490 as "FIXED" are that we pass.
http://www.w3.org/Graphics/SVG/Test/20061213/htmlObjectHarness/full-fonts-elem-01-t.html
and tests 77, 78 and 79 of the Acid3 test suite.
You need to log in
before you can comment on or make changes to this bug.
Description
•