On 28/06/12 12:13, Derric Atzrott wrote:
I just wonder: Why do we not simply transmit the SVG image, but render a
png for an SVG-file to the browser? Historic reasons?
I think it is because there is no good way for us to know if a browser supports SVG images other than having a list of user-agents that do and checking that way.
We don't want to send an SVG image to a browser that is unable to render it. Someone correct me if that was wrong.
Thank you, Derric Atzrott Computer Specialist Alizee Pathology
Here's the Mozilla developers' take on this, as of April this year:
https://bugzilla.mozilla.org/show_bug.cgi?id=240493
I'm not sure I agree with them, as this seems to defeat the entire point of the Accept: header, and makes browser-sniffing compulsory if you want to use SVG (or you risk breaking all old browsers), but there we are.
-- N.