Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with this on IE, Chrome, and Firefox #1

Open
kenbuja opened this issue Aug 22, 2013 · 5 comments
Open

Issues with this on IE, Chrome, and Firefox #1

kenbuja opened this issue Aug 22, 2013 · 5 comments

Comments

@kenbuja
Copy link

kenbuja commented Aug 22, 2013

I've tried this application in different browsers and each shows a different issue

IE (9.0.8112)
No basemap initially, but get annotation. Basemap appears if I zoom in or out. No pictures drawn and the console logs "LOG: debug: esri.layers.FeatureLayer: unable to find 'Link' field in the layer 'fields' information [url: ]"
instamap_ie

Chrome (28.0.1500)
When a photo is clicked, the map pans to another location
Before
instamap_chrome_before
After
instamap_chrome_after

Firefox (17.0.8)
When a photo is clicked, the mouse "sticks" to that location and the map will pan as the mouse moves. This will stop when the mouse reaches the edge of the map div.

@ctourret
Copy link
Contributor

The console error is present on all browsers, but does not affect the app

Not tested with IE, I will test it tomorrow on IE10 because IE9 does not support Web Socket
Under Firefox 23.0.1/MacOS 10.8.4, I can reproduce the mouse sticking on the picture after clicking
Under Chrome 28.0.1500.95/MacOS 10.8.4, it works fine
Under Safari 6.0.5/MacOS 10.8.4, I can reproduce the mouse sticking on the picture after clicking
and on my iPhone, it works, except the Mouse in and out event for obvious reason

@kenbuja
Copy link
Author

kenbuja commented Aug 22, 2013

I tried this again on Chrome 29.0.1547.57 and it exhibits the same behavior. This is on Windows 7 Enterprise, Service Pack 1.

@ctourret
Copy link
Contributor

But on the GeoEvent Processor side, it works great :
image

@ctourret
Copy link
Contributor

I've commented the mouse down event in the repo and the gh-page, while looking for a fix...

@ctourret
Copy link
Contributor

It was event bubbling that was causing the problem, fixed by using the Dojo event.stop(e) method. Tested successfully on IE10. Not working with IE < 10 due to lack of Web Sockets support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants