Pre-3.0 API and Latest Chrome

[AllenAnselmo]

Hey all,

Not sure how much this affects any of you, but I thought I'd post it either way to get the information out there. It seems that the latest version of Chrome (29.0.1547.57 m) that came out Tuesday or so, has made some change which causes pages with older ESRI Javascript API versions (pre-3.0) to fail to load due to some sort of errors being triggered in the contenPane loading code of dojo it seems.

It doesn't seem to be affecting our pages that are more up to date (3.5+) but we have some older ones in production which lock up entirely on load in Chrome now and weren't doing so last week, whereas they load fine in the latest Firefox and IE browsers.

Anyone else running into this situation or even have any older pages in production that haven't gotten upgraded?

If so, be sure to put in a bug report to Chrome through the Menu > Tools > Report an Issue tool, since the more they get in, the more likely they are to fix whatever they broke so abruptly.

[BetsySchenck-Gardner]

We are using 2.8. Thanks for looking into this.

[derekswingley1]

Thanks everybody. We're testing fixes.

We do not plan to modify what's currently hosted on serverapi.arcgisonline.com but will likely post patched versions of the API on js.arcgis.com. Applying the fix will require you to change the URL your app uses for the JS API. For instance, if you use 2.8 from serverapi:

<script src="http://serverapi.arcgisonline.com/jsapi/arcgis/2.8/"></script>

To get a patched equivalent, once we upload patched versions, you'll update your app to use:

<script src="http://js.arcgis.com/2.8/"></script>

I'll post here when we're further along in this process and/or if anything changes. Thanks for being patient.

[Zhifeng__Jeff_Tang]

We are using JSAPI v2.1 and both IE 10 and Chrome have issues.

[KellyHutchins]

zhifengtang,

IE10 is not supported at version 2.1 of the API. If you need to support IE10 you'll have to upgrade to version 3.4 or greater.

We are using JSAPI v2.1 and both IE 10 and Chrome have issues.

[derekswingley1]

Here's a very simple workaround:  before your script tag that references the JS API, include this in a script tag:

// fix for https://bugs.dojotoolkit.org/ticket/17400
!document.firstChild.children && (document.firstChild.children = true);

Ideal place would be where you define dojoConfig.

Here's a working example:  http://jsbin.com/OmUjAmI/1