I'm using the editor widget, JS SDK version 4.27.6
The update button is not working.
- Clicking the button is not triggering any HTTP requests or doing any actions.
- No errors in the console.
Is this a common bug?
I'm encountering something similar after upgrading to JS API 4.28. When resizing/reshaping lines or polygons I got the save/update button becomes useless and no event is triggers in Developer Console.
The only thing I have to add is that if I move the line or polygon a little bit before start vertex editing then the buttons work. I've offered that workaround to my users but would still want a full fix.
Did a simple `npm install zone.js@0.14.5` and it also fixed the issue in my 17.3 app.
The latest update to zone.js includes the fix for this issue: https://github.com/angular/angular/blob/main/packages/zone.js/CHANGELOG.mdJust did a `yarn upgrade-interactive` to get the latest version of zone.js in our Angular 17.3 app, and I can confirm that this fix resolves the issue for our app. Your package manager command and results may vary 🙂
It should be released with version 18, yeah. Installing 18.0.0-next won't actually help (I tried it a week or two ago) because the actual fix is in zone.js, not the angular library (zone.js is just inside the angular repository). We'll need them to publish a new/beta/rc of zone.js to get the fix, or you could install the package directly from the repo.
That is my understanding at least.
The Angular issue that seems to be a the root of this was fixed, but the fix is not present in the latest version of Angular (17.3, at the time of this comment). The commit with the fix has tags that reference version 18, which (if I'm reading that correctly), means it's slated to be included in version 18, but was not back-ported to 17. However, I can't find that commit or issue referenced directly in the changelog.Hoping that version 18 will resolve this. Might even go ahead and install `18.0.0-next` and see if that fixes the issue. I don't love the workaround that breaks zone for every "(click)" in our app.
Does anyone know if the issue is fixed in the SDK now as well? I assume it would require that the library updates angular?
FYI, the angular issue at the core of this problem was just fixed and merged, so I imagine it'll be included in the next release.
solved, thank you very much
Yes, my app is made with Angular
thank you!
Not sure if any of you are using Angular like I am, but Esri have added some details about this issue finally:
This issue does not appear to be fixed in the latest version of 4.28 either (4.28.10 at the time of this comment).
I too am having issues with this. I assume no resolution has been found?
This solution is not acceptable, @Esri are you going to solve it in the next version?
Same thing for me. Moved to Firefox until this issue is fixed. The samething appears with the compass. It works fine in Firefox, but it can out of nowhere stop working in chrome and Edge.
The solution for me currently is that it works fine in Firefox bot not in chrome or Microsoft Edge.
I see that this topic is stopped, any solution?
I'm having the same issue. I did just realize the editor works in Firefox but not in Chrome (which is what I normally use for development) -- is that the same for you all, and has anyone found a fix?
No, we decided to not upgrade for now... Hope it gets fixed soon.
I am encountering the same problem with the ArcGIS API Editor widget for JavaScript version 4.27.0. Like you, when I click the update button, no HTTP request is initiated and no action is taken.
Here are a few things I have checked so far:
Making sure the layers have editing enabled on the server side.
I'm still working on the problem, but I was wondering if you've had any success since your post. If you've found a solution, I'd love to hear about it.
Same problem here. Looks like the bug was introduced between 4.26.5 and 4.27.1
I was able to fix it by rolling back to version 4.24. Not ideal but the bug is not documented at this point. I'm not sure if it has been reported yet.
I'm encountering the same issue here. Have you found a solution to this problem?
Kind regards,
Nicolas
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
