If we're not 100% compatible with SVG, why would they oppose an
improvement like the suggested one?
Content that uses childElements[...] would not function correctly
in SVG Tiny 1.2 implementations for no particularily good reason.
I'm not following this argument at all. Neither would content that uses
.globalStorage, .forms, .querySelector or anything else that's not in
the SVG Tiny spec.
We're trying to make a new API here, of course content that uses that
API isn't going to work in implementations that don't support it.
/ Jonas
