search

google-code-export / svgweb

Automatically exported from code.google.com/p/svgweb
Other
1 stars 1 forks source link

If Adobe SVG Viewer is installed, IE8 will prompt for permission to use it on SVG Web sites #198

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install Adobe SVG Viewer. It can be enabled or disabled.
2. Load the demo.html in IE8

What is the expected output? What do you see instead?

When web page comes up, IE8 will ask you if its OK to install and use the 
Adobe SVG plugin for this web site. This appears as a yellow toolbar 
prompt. If I remove the Adobe plugin entirely (from control panel 
Install/Remove software), the prompt does not occur. (Gee thanks IE8! I 
feel so much more secure knowing IE8 will force users to "install" and 
approve using a plugin... which was actually already installed and 
enabled.)

This probably won't affect a lot of users and may not be fixable, but it 
is probably worth looking into whether we can stop IE from doing this.

Original issue reported on code.google.com by grick23@gmail.com on 31 Jul 2009 at 12:26

GoogleCodeExporter commented 9 years ago 
Please recheck this.  I think demo.html is now working in IE w/ Adobe SVG 
Viewer (ASV).

If you follow the directions in the users manual carefully the flash version 
will
always come up.  I have not tested the inline svg via <script> though.
In a HTML file if you use:
<!--[if IE]>
<object id="testSVG" src="embed1.svg"
        classid="image/svg+xml" width="500" height="500">
<![endif]-->
<!--[if !IE]>-->
<object id="testSVG" data="embed1.svg"
        type="image/svg+xml" width="500" height="500">
<!--<![endif]-->
</object>

it works because the ASV does not support SVG in an object element (security 
issue).

The second method described in the section:
"Dynamically Creating and Removing SVG OBJECTs and SVG Roots"
also works for me.  This is the method I used in the attachments in issue 270.  
The
<body> is blank except for the onload="init()"  The entire display is built via 
JS. 
I went this way because my application is created from XML via XSLT on the fly 
every
time and the first method is almost impossible to create via XSLT.

This is an important bug though.  I recoded my application to make sure it 
wouldn't
hang if the user had the ASV installed.

Original comment by bruce.ri...@gmail.com on 11 Sep 2009 at 10:04

GoogleCodeExporter commented 9 years ago 
Nice; so it sounds like you've found a valid workaround to prevent ASV from 
popping up?

Original comment by bradneub...@gmail.com on 11 Sep 2009 at 11:04

GoogleCodeExporter commented 9 years ago 
> it works because the ASV does not support SVG in an object element (security 
issue).

I did read something about that but I believe it is a mostly a myth: I've been 
using
this approach [1] for a while now... Yes, this unveils that IE's object
implementation is basically an embed wrapper, but object allows having fall-back
content, which is pretty important to notify users about missing SVG support.

[1] http://joliclic.free.fr/html/object-tag/en/object-svg.html

Original comment by helder.magalhaes on 12 Sep 2009 at 7:39

GoogleCodeExporter commented 9 years ago 
Helder
As usual you are right.  You can use the object element - however scripting is
disbled [1].

Back to the topic, I would suggest marking this as WONTFIX.  If you install the
viewer you have an option to use the plugin on all pages (yes including a SVGWeb
page).  Once you do this, the popup will go away. This is the way most people 
will
use ASV anyway.  The important thing is the two programs don't seem to collide. 
 I
have the viewer installed and the flash version will come up when the methods 
from
the Users Guide are used.  Has anyone found a conflict?

[1] http://www.adobe.com/svg/viewer/install/

Original comment by bruce.ri...@gmail.com on 16 Sep 2009 at 7:34

GoogleCodeExporter commented 9 years ago 
> As usual you are right.

A lucky guess... ;-)

> You can use the object element - however scripting is disbled

This is another weird claim. I've been using ASV3/6 in IE-based deployment for a
while (ranging from IE6 to IE8), with SVG scripting in most and even HTML<-->SVG
script communication in some, and everything works as expected.

Sorry if this is going somehow off-topic, but maybe something useful (a test 
case,
anyone?) will bubble from the discussion. :-)

Original comment by helder.magalhaes on 16 Sep 2009 at 10:59