I'm encountering an interesting problem that appears to be limited to MAC users running OSX. We have a wilderness map, built using the JavaScript api, that overlays an ArcGIS map service of wilderness boundaries that we run on top of a choice of basemaps. OSX users can see the basemaps, but the boundaries don't show in any browser (users tested safari and firefox). One particular user has both OSX and windows on his MAC and was able to view both of the maps below successfully when running windows but not when running OSX!
So OSX users can't see the wilderness boundaries on either of the following, both of which use the map service above. Maps work fine for windows users.
These same OSX users who can't see the boundaries on the above maps CAN see them on the scaled down test maps I've created to help diagnose this problem.
I'm wondering if there's some sort of timeout issue with the full map, which is more feature-rich than the test maps, and thus takes longer to fully load? Could it be something else? Thanks for any suggestions folks have to offer.
SOLUTION! I got the user to use firebug and the net tab revealed that the service was giving a 404 error because the image width was out of range. Turns out this particular user had a 27in monitoring set at 2560 x 1440. For some reason when he was running OSX, launching the map at full screen gave this error. I'm not sure why it didn't do so when he was running windows. We increased the sizing in the service settings and it worked fine.
SOLUTION! I got the user to use firebug and the net tab revealed that the service was giving a 404 error because the image width was out of range. Turns out this particular user had a 27in monitoring set at 2560 x 1440. For some reason when he was running OSX, launching the map at full screen gave this error. I'm not sure why it didn't do so when he was running windows. We increased the sizing in the service settings and it worked fine.