Hi all,
I was tracking down why the 'super' and 'sub' script text in
the flow text examples isn't super and sub scripted and I found it.
The new SVGTextElement bridge checks if the elements are subclasses of
the 'SVGOMTextPositioningElement' class, if they are then it adds the 'x',
'y',
'dx', 'dy', and 'rotate' attributes to the Attributed string. However in
this case
the flowSpan element really only supports dx,dy and perhaps rotate
(absolute positioning is not a good idea).
I can think of three solutions:
1) introduce a new interface or class that defines just the
dx/dy/rotate,
and have the span elements implement that.
2) Just make the span elements subclass SVGOMTextPositioningElement
and not worry about the 'x' & 'y' support.
3) Chalk the whole thing up as a loss anyway since the WG has moved
in another direction.
Normally I'd be inclined towards 3, except this is a true regression
(reasonable content that worked previously would stop working).
My leaning is towards 2 since it's simple and the whole thing is a
loss anyway ;) One is probably "the right thing" except the whole
thing is a loss anyway and it's not clear we will want to keep the
"albatross" once the WG points the correct direction.
Any opinions from the peanut gallery?
