How does TRIRIGA determine that there is no native SVG present?


What is TRIRIGA looking at to determine that there is no native SVG present?

Starting with 3.4.2, TRIRIGA supports browsers that have native SVG support.  So we basically just put an <object type=”image/svg+xml” …> and fill out the rest whenever we want to render SVG.  If for some reason the browser does not support native SVG, then we have text behind it that will show the message “Current browser does not support native SVG”.  All the browsers listed in our support matrix should support native SVG.  If you are seeing this message, you might want to double check our support matrix and, for IE in particular, verify what rendering mode IE is using. In particular, we do not support compatibility mode in IE in 3.4.2 and later.

[Admin: This post is related to the 12.04.15 post about supporting native SVG.]

Continue reading

One thought on “How does TRIRIGA determine that there is no native SVG present?

  1. Pingback: Why doesn’t IE11 support SVG when using TRIRIGA 3.4.2 or later? | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s