New topic: 

Problem starting RSW app under IE9 (comp view) Chrome Frame

<http://forums.realsoftware.com/viewtopic.php?t=46228>

         Page 1 of 1
   [ 3 posts ]                 Previous topic | Next topic          Author  
Message        richardschmidt          Post subject: Problem starting RSW app 
under IE9 (comp view) Chrome FramePosted: Thu Dec 13, 2012 9:26 am              
           
Joined: Tue May 31, 2011 1:42 pm
Posts: 13                I have a problem with running my RSWEB app on some 
Windows/IE9 configurations. On some confirurations IE9 delivers a Google page 
that says I have to install Google Chrome Framework when I start my application 
(generated cgi on linux server).

This only occurs on IE9 configurations that report "IE9 compatibility view" 
when I look into the F12-developer tools. When I set this mode to "IE9 
standard" the application just runs fine (without the GCF).

When I look at the HTML-header of a generated page by my RSWEB application it 
says <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">. When I add 
the metatag <meta http-equiv="x-ua-compatible" content="IE=9"> to the 
HTMLheader property of my application that does not seem to force the mode of 
the IE9-broswser to "IE9 standard"

When I look at the header of the HTML page I can see both metatags (standard 
metatag and my own metatag) but the latter does not seem to overrule or 
override the first one "IE=edge" in the beginning of the HTML header.

Chrome and FF work fine. How dow I deal with this IE9 mode. I cannot expect my 
IE9 users to instala Google Chrome Framework first before using my application.

BTW, I do not have this behaviour with my other RSWEB apps. They all work fine 
when the mode is set to "IE9 compatibility view". I already removed all the 
monkeybread plugins from the plugins folder (to exclude a specific problem with 
these plugins). Could it be the use of a specific standard UI control that 
forces the use of the Google Framework?

I hop you can help me. Thanks in advance.      
_________________
RealStudio Web 2012r2 | MonkeyBread | MacBook Air OSX Lion 10.8 | CentOS VPS / 
WHM*CPanel

My RealStudio Web applications are available at http://www.runapps.nl/english/ 
(Dutch language apps only)  
                             Top                Stretch          Post subject: 
Re: Problem starting RSW app under IE9 (comp view) Chrome FrPosted: Thu Dec 13, 
2012 1:56 pm                       Real Software Engineer          
Joined: Tue Jul 14, 2009 4:33 pm
Posts: 56
Location: Jacksonville, FL                I can't think of any particular 
control that would cause it to demand ChromeFrame on IE9. The only thing I can 
think of would be if a user had an extension that caused IE to identify itself 
as an older version of IE (like IE6 or IE7).      
_________________
Greg O'Lone
Software Engineer
Real Software  
                             Top                richardschmidt          Post 
subject: Re: Problem starting RSW app under IE9 (comp view) Chrome FrPosted: 
Thu Dec 13, 2012 2:33 pm                         
Joined: Tue May 31, 2011 1:42 pm
Posts: 13                Nope, these are all Windows7/IE9 configurations 
(several). It's only giving problems on some configurations where browser mode 
= "Interne Explorer Compatibility View".



I made serveral applications and none give the same problem on this 
configuration and browser mode. It is only one specific application.      
_________________
RealStudio Web 2012r2 | MonkeyBread | MacBook Air OSX Lion 10.8 | CentOS VPS / 
WHM*CPanel

My RealStudio Web applications are available at http://www.runapps.nl/english/ 
(Dutch language apps only)  
                             Top             Display posts from previous: All 
posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost 
timeSubject AscendingDescending          Page 1 of 1
   [ 3 posts ]      
-- 
Over 1500 classes with 29000 functions in one REALbasic plug-in collection. 
The Monkeybread Software Realbasic Plugin v9.3. 
http://www.monkeybreadsoftware.de/realbasic/plugins.shtml

[email protected]

Reply via email to