-
Notifications
You must be signed in to change notification settings - Fork 18
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
Warn on unsaved changes doesn't work #102
Comments
I have the same issue. @sejal27 did you find a way to ignore unsaved changes? |
I have the same issue: Apex 19.1.0.00.15 and Select2 version 3.0.3. Traced down that it happens when "Display null value" is set to NO So workarund is to leave "Display null value" to YES on SELECT2 item when "Warn on Unsaved Changes" is set to "Ignore". The reason is that To repeat it set "Execute when Page Loads" to :
In apex "desktop_all.min.js?v=19.1.0.00.15" the situation happens in function "apex.item(x).isChanged()" here as p(): |
@tonupold just a debugging tip, if you turn on Debug on the page, the desktop_all.min.js file will get exploded into all the un-minified individual components making it very easy to track the correct code. |
In Apex 18.2 we still found this issue when using Select2 plugin. |
I replaced my current multi select item with select 2 plug in and it had Warn on Unsaved Changes set to Ignore. But when I refresh the page, it still prompts for unsaved changes.
The text was updated successfully, but these errors were encountered: