[Geomoose-users] MS Explore 10 issues

[Jim Klassen]

It also appears to me that at least the demo at www.geomoose.org (which is actually newer than 2.6.1 despite what it says) appears to work in IE10 and is detecting correctly as HTML5 (IE10 Standards mode).

There appear to be some IE10 fixes in the dojo 1.6 branch that have been back-ported from 1.8 but haven't made it into a 1.6.2 release yet.  If necessary we could look at including these in GeoMoose, but I'd prefer to stay at dojo-1.6.1 (rather than a newer unreleased intermediate version) unless someone can show me something particular that it would fix.

On Apr 10, 2013, at 9:43 AM, Johan Forsman wrote:

> For what it’s worth I have a 2.6.1 installation on MS4W and it appears to operate normally using IE10 based on first impressions.
>  
> From: geomoose-users-bounces at lists.osgeo.org [mailto:geomoose-users-bounces at lists.osgeo.org] On Behalf Of James Klassen
> Sent: Tuesday, April 09, 2013 7:15 PM
> To: Paul Wickman
> Cc: geomoose-users at lists.osgeo.org; Tim Hennig
> Subject: Re: [Geomoose-users] MS Explore 10 issues
>  
> No need to just wait and hope the issues sort themselves out... Feel free to offer patches.  At least for Duck and myself it is particularly difficult to test and debug against IE and especially IE 10 (usually involving spinning up a temporary EC2 instance).  Help in this regard would certainly be appreciated.
> 
> I did some quick tests with 2.6.1 against IE10 beta awhile back and it didn't work.  It is rather frustrating since it works with IE9, FF and WebKit.  At the time I couldn't find any diagnostics in IE10 that indicated what it didn't like so I gave up.
> 
> 2.4 has a number of known CSS issues with patches published to the list and are in the 2.4 svn branch.  At the moment, there doesn't seem to be enough interest in a 2.4.1 release without specific funding. (There are a few other bug fixes related to MapScript 6 that need to be worked out that should also go into 2.4.1 that are no fun to fix.  There have been no user submitted patches and the core developers projects/needs have moved to 2.6.x.  I for one am not going to spend a bunch of time for free working on something I'm not interested in.)
> 
> On Apr 9, 2013 6:36 PM, "Paul Wickman" <paul at flatrockgeo.com> wrote:
> Tim,
>  
> We've got some GM v2.4 instances with similar problems.  We've had to tell IE v10 users to view their site in Compatibility Mode, which seems to work for them.  Certainly not a long term solution, but we've been waiting to do any GM v2.6.1 upgrades until a few more of these sorts of issues get sorted out.
>  
> -Paul
>  
>  
> 
> On Tue, Apr 9, 2013 at 6:20 PM, Tim Hennig <timhbellevue at gmail.com> wrote:
> Hi,
>  
> I would like to know if anyone had issues with GeoMoose 2.6.1 and MS Explore 10.
>  
> My computer updated MS explore 9 to 10 and started noticing some issues.
>  
> Some issues are:
>  
> 1.  No data display, I can see the legend, etc in catalog.
> 2.  Extreme data view extent.
> 3.  Commands buttons and searches, etc are non-responsive .
>  
> Any ideas?
>  
> I ended up reverting back to MS Explore 9.  Everything worked after the downgrade.
>  
>  
>  
> Thank You,
>  
> Tim
> -----------------------------------------------------------------
> Tim Hennig
> GIS Coordinator
> 
> Community Development Department
> Village of Bellevue
> 2828 Allouez Avenue
> Bellevue, WI 54311
> 
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
> 
> 
> 
>  
> -- 
> Paul Wickman
> CTO | Flat Rock Geographics
> 612.280.5850 | paul at flatrockgeo.com
> www.flatrockgeo.com | twitter.com/flatrockgeo
> 
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20130411/40ff5fe3/attachment.html>