Firefox problems loading a map for only some users?

Question

I have a map that works for most users in Firefox, IE and Chrome.  I have reports from a handful of users they can't properly open this map in Firefox, even when we have the same version of Firefox, in this case version 30. I believe it has to do with something in their Firefox browser, maybe a setting or permission, that is different than mine.  The majority of people who have tried it all report it opens just fine.  We've tried comparing our configurations, but haven't spotted anything yet that is different between computers.

They receive an error  ReferenceError: require not defined.

https://ogi.oa.mo.gov/MDA/ControlPoints/index.html

I have been told that I must use https for all maps, even though we only occasionally have something with any secure data.  I don't know if that is part of the problem or not.  I don't think this is something I can fix in the code.  I'm baffled what to tell these users, besides "use something besides Firefox".  It's worked fine on my computer through more than one upgrade to my Firefox browser.  Is there some thing we could look at in terms of Firefox settings that might help?

KonstantinLapine · Answer

That sounds like quite a hack.  That makes me think about my configuration, though.  I remember reading somewhere that I should now be adding async:true to my dojoConfig definition.  I thought that was the default, but lately I heard the default was actually async:false.

I realize you may not want to load your scripts dynamically so I answered in the other thread:
http://forums.arcgis.com/threads/85485-quot-Uncaught-ReferenceError-require-is-not-defined-quot-when-adding-JSAPI-after-page-load?p=399631#post399631

TracySchloss · Answer

I've been having strange Firefox behavior this week, so this morning I decided to trace down the problem I was having (Firefox thought it had an instance already running when I come in in the mornings.  I didn't.).  Through tracking down that problem, I followed steps to reset Firefox.  This turned out to be a bad idea, but as a consequence, I noticed that I too was seeing a problem with my code not even getting into the lines for dojo.require before it bombed.  Not only that, but my security certificates files Firefox uses wouldn't let me add Firebug back in again.  Like I said 'Bad idea'.

I dug the certificates out of the backup I had and put them in my new profile.  Lo and behold, I could get my Firebug added back in, but also my dojo.require was OK again.

If the internal help person who deals with the certificates for the web browsers gets back with me, maybe we'll get to the bottom of this and I'll post our findings.

TracySchloss · Answer

That sounds like quite a hack.  That makes me think about my configuration, though.  I remember reading somewhere that I should now be adding async:true to my dojoConfig definition.  I thought that was the default, but lately I heard the default was actually async:false.