308360 - tspan bugs/missing features

Status: RESOLVED FIXED

(Core :: SVG, defect)

Description

[Martin Kroeker]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.1 (like Gecko)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

The mozilla svg status page does not explicitly mention that the 
baseline-shift attribute is not implemented. 
Trying to work around this for sub/superscripts, i noticed that 
- <tspan y="..."> resets the x position to the start of the string instead 
of keeping its current value when no new x="..." is given 
- when changing the font-size in a tspan, the text length is apparently not 
calculated correctly, creating a large gap around smaller characters   

Reproducible: Always

Comment 1

[Ognyan Kulev]

This is duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=308338

Comment 2

[Ognyan Kulev]

Actually, it's not duplicate, it's about different bugs. Sorry for the noise.

Comment 3

[Adrian Frischauf]

If I understand correctly this is exactly the missing feature I am also 
experiencing right now. To make it a little more clear here an example 
of what will go wrong. The following code snipet:

<tspan x="10 20 30 40">HELP</tspan>

I expected this piece to be rendered with each character at the given
x position. What happens is that the first character is put at the
proper location but the other ones are just put using the standard
characterwidth but not the given position. It has nothing to do with the
baseline-shift attribute.

Comment 4

[Robert Longson [:longsonr]]

(In reply to comment #3)
> If I understand correctly this is exactly the missing feature I am also 
> experiencing right now. To make it a little more clear here an example 
> of what will go wrong. The following code snipet:
> 
> <tspan x="10 20 30 40">HELP</tspan>
> 
> I expected this piece to be rendered with each character at the given
> x position. What happens is that the first character is put at the
> proper location but the other ones are just put using the standard
> characterwidth but not the given position. It has nothing to do with the
> baseline-shift attribute.
> 

You are describing a different bug i.e. bug 311986. This bug is about resetting the x position in different tspan fragments.

Comment 5

[Robert Longson [:longsonr]]

Fixed by bug 333698