instead of:
if (oldLat != lat || oldLng != lng) {
this.$el.trigger('change');
}
it should be:
if ( oldLat != lat || oldLng != lng ) {
this.$el.find('.input-lng').trigger('change');
}
hi daron, attached the new version. I think the problem is fixed now.
Triggering the change on the element is not enough. It need to be triggered on the field. Now it looks good.
hi daron, i attached the file to this message.
hmm, i also tried that, but it triggers the changes correct for me.
following piece of code, put after setting the lat lng fields (line 3927), fixes all problems for me.
// fire the change trigger only on real changes
var oldLat = this.$el.find(‘.input-lat’).val();
var oldLng = this.$el.find(‘.input-lng’).val( lng );
if (oldLat != lat || oldLng != lng) {
this.$el.trigger(‘change’);
}
Would be fine to have this fixed in one of the next releases.
Ok, i think i found the reason of this issue.
On creating the map function render of javascript file js/input.js on line 3775 is called.
After creating the map this.update( lat, lng ).center(); is called.
And here on line 3928 the lat and long fields are set with the same values as they already have and a change trigger called. Thats the reason why the page thinks about changes.
uncommenting the .trigger(‘change’); in line 3930 fixes the problem.
the only problem is that changes are not caught, if there are real changes. IMHO the change trigger only should be called on real changes and not on initialization.
hi daron, i gave that a try, but the issue also occures on a fresh install.
Everything’s working fine without an address entered in the map.
As soon as you add an address the page asks if you really want to leave without any changes done on editing the page.
I see the sama issue in my installations. Also did the update to 5.0.9, but the problem still exists
input.js1.zi....zip