Snapping not working for edit feature in Google Chrome

[KapilKhisa]

Hi All,

I am using this application to test the snapping functionality in edit feature.

Default Editor 

When editing a point feature, the snapping works fine in Firefox and IE browser but doesn't work in Chrome.

Any help will be appreciated.

Thanks,

Kapil

[PanagiotisPapadopoulos]

The problem submitted as  Bug.

[DarkoRadiceski]

Thank you for your assistance so far. Much appreciated. Did the team indicate any potential turnaround for the fix? If it helps we are happy to raise it with the local ESRI Distributor here in Australia. 

[PanagiotisPapadopoulos]

I am not sure when this is planed to be fixed.

You can try through the local Distributor for a fix, the BUG id is 000102090.

[DarkoRadiceski]

Hi guys

Is there any news if there has been a fix applied to this snapping issue?

Sincerely

Darko

[PanagiotisPapadopoulos]

Hi Darko

According to bug status fixed on version 3.20

BUG-000102090: JavaScript 3.19 graphic snapping does not work in Go.. 

[GeraldSilva]

I've run in the same problem and found this discussion. Using 3.21 an Chrome 60.0.3112.113 (Versão oficial) 64 bits.

In Edge is working fine, any workaround?

[PanagiotisPapadopoulos]

Hi Gerald,

Running on the same Chrome version the following sample Default Editor snapping is working. Use the button Ctrl to enable snapping during the editing session.

[GeraldSilva]

Hi Panagiotis,

thanks for your response.

sorry for not being clearly, snapping is working, but not correctly in some cases:

I've made an example:

[removed]

For example, if you create a new line (bramar.db.Plinks) and snap click the first point (bramar.db.Pnodes) everything it's ok, already the second point (double clicking) he creates a vertex on the snapped point and finishes the line on the real click coordinates instead of the snapped feature. This happens only in chrome.

Best regards,

Gerald