Closed
Bug 897884
Opened 12 years ago
Closed 12 years ago
dominant-baseline attribute should not be inherited
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pom, Unassigned)
References
Details
Attachments
(1 file)
|
252 bytes,
image/svg+xml
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212
Steps to reproduce:
An SVG tspan element inside a text element that has a dominant-baseline attribute inherit its parent value, where the spec says that it should not. See the attached file for an example.
Actual results:
The string "Hello there" appears centered on the red line.
Expected results:
The string "Hello there" should appear above the red line. It does in Chrome, Opera and Safari.
Updated•12 years ago
|
Comment 1•12 years ago
|
||
> An SVG tspan element inside a text element that has a dominant-baseline
> attribute inherit its parent value, where the spec says that it should not.
Reading the spec http://www.w3.org/TR/SVG11/text.html#DominantBaselineProperty you are right, the value is not really inherited. But the default value is “auto”, and the description for that states:
> If this property occurs on a ‘tspan’, ‘tref’, ‘altGlyph’ or ‘textPath’ element,
> then the dominant-baseline and the baseline-table components remain the same as
> those of the parent text content element.
The way I read this, the value on the CSS level is “auto” but the actual position is still inherited. Might be I'm misreading this somehow, but if so, it would be nice to know where that mistake lies, in order to get “auto” implemented right.
Comment 2•12 years ago
|
||
(In reply to Martin von Gagern from comment #1)
> The way I read this, the value on the CSS level is “auto” but the actual
> position is still inherited. Might be I'm misreading this somehow, but if
> so, it would be nice to know where that mistake lies, in order to get “auto”
> implemented right.
Me too. Anyone who still thinks this is wrong should take this up with the w3c svg working group.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•