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

Locate Button HTML Tags #341

Closed
faridcher opened this issue Jan 6, 2015 · 6 comments
Closed

Locate Button HTML Tags #341

faridcher opened this issue Jan 6, 2015 · 6 comments
Labels

Comments

@faridcher
Copy link

When using "Locate Button", I get the result like the following image:

snap

The widget treats the html tags as plain text.

@tmcgee
Copy link
Member

tmcgee commented Jan 7, 2015

I can confirm this is what I see as well. I believe this used to work fine though not sure when something changed to cause.

@tmcgee tmcgee added the bug label Jan 7, 2015
@acbassil
Copy link

acbassil commented Jan 9, 2015

How can I turn it off?

@acbassil
Copy link

acbassil commented Jan 9, 2015

The popup

@faridcher
Copy link
Author

You can do it easily by setting publishGPSPosition property to false. Modify the viewer.js file like this:

locateButton: {
                include: true,
                id: 'locateButton',
                type: 'domNode',
                path: 'gis/dijit/LocateButton',
                srcNodeRef: 'locateButton',
                options: {
                    map: true,
                    publishGPSPosition: false,
                    highlightLocation: true,
                    useTracking: true,
                    geolocationOptions: {
                        maximumAge: 0,
                        timeout: 15000,
                        enableHighAccuracy: true
                    }
                }
            },

jebu75 pushed a commit that referenced this issue Jan 13, 2015
locate button displays html tags in message as text.  Also, cleans up altitude accuracy label in locate button template.
@jebu75
Copy link
Collaborator

jebu75 commented Jan 13, 2015

If you like, please test the fix I just submitted in #344 and let me know if that fixes the issue for you. Thanks!

DavidSpriggs added a commit that referenced this issue Jan 13, 2015
@faridcher
Copy link
Author

The fix is working fine. Thanks

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

No branches or pull requests

5 participants