On 5/9/06 5:35 AM, Robin Berjon wrote:
> On Jan 25, 2006, at 18:41, T Rowley wrote:
>> The SVG 1.1 DOM has a matrix creation method of SVGSVGElement that
>> corresponds to the methods of other base types, namely:
>>
>> SVGMatrix createSVGMatrix();
>>
>> The SVGT 1.2 uDOM replaces this with createSVGMatrixComponents(...),
>> which seems like a needless incompatibility that authors will need to
>> deal with when adapting 1.1 content to 1.2t. I suggest switching back
>> the 1.1 DOM method of matrix creation.
>
> In this case it's a choice between one incompatibility and another. This
> specific API is what is supported by JSR-226, and the SVG WG is
> committed to being compatible with that. Ideally, JSR-226 would have
> been more compatible with Full 1.1, but unfortunately while that was
> largely made to happen, in some cases it wasn't possible. JSR-226 is a
> stable specification, and phones are already shipping with it. We
> therefore decline to make the change.
I find it highly disappointing that the SVG WG places a higher priority
getting compatibility with JSR-226 than an earlier SVG specification.
I'm inclined to say that the incompatibility problems are the JCP's
problem, not the working groups'.
The reasons for objecting to the changes are still valid, I think.