It would be great if someone could come up with a "fix" for this...
this happened to us on arcgis.com today. Switching to IE fixed it.Did not clear cache
Do you have any additional info? I'd really like to be able to reproduce this.
JavaScript API team... is this something you're able to fix in the API or is this an inherent issue with Chrome and Firefox?
Seems this is an issue we are getting reported to us by more and more users of Windows touch enabled machines. Any update on if this has been addressed on the API level? Still seems to be an issue with the latest Chrome v36 and ESRI JS v3.8
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.