You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'DocumentConversionSettings-ChosenFolderID' field is causing the silverstripe/admin jquery.changetracker.js to mark the page as changed when there are no changes in Chrome. This does not happen in Firefox.
Versions
silverstripe/documentconverter: 2.3.0
silverstripe/admin: 1.11.3
Chrome: Version 110.0.5481.178
PHP: 8.1
Details
In Chrome, the changetracker records the initial value of the field as: {"name":"DocumentConversionSettings-ChosenFolderID","value":""}
After the TreeDropdownField finishes loading this changes to: {"name":"DocumentConversionSettings-ChosenFolderID","value":"0"}
The no-change-track class is added to the field holder <div> for this field but is not on the actual <input> field, which is where the changetracker is looking for that class:
This is therefore appearing as a changed field, causing the save/publish buttons to become active and triggering the browser warning that changes will be lost when the user tries to navigate away from the page even when no changes have been made.
In Firefox, the field value starts as "value":"0" and therefore does not trigger this issue.
The text was updated successfully, but these errors were encountered:
Summary
The 'DocumentConversionSettings-ChosenFolderID' field is causing the silverstripe/admin jquery.changetracker.js to mark the page as changed when there are no changes in Chrome. This does not happen in Firefox.
Versions
silverstripe/documentconverter: 2.3.0
silverstripe/admin: 1.11.3
Chrome: Version 110.0.5481.178
PHP: 8.1
Details
In Chrome, the changetracker records the initial value of the field as:
{"name":"DocumentConversionSettings-ChosenFolderID","value":""}
After the TreeDropdownField finishes loading this changes to:
{"name":"DocumentConversionSettings-ChosenFolderID","value":"0"}
The
no-change-track
class is added to the field holder<div>
for this field but is not on the actual<input>
field, which is where the changetracker is looking for that class:This is therefore appearing as a changed field, causing the save/publish buttons to become active and triggering the browser warning that changes will be lost when the user tries to navigate away from the page even when no changes have been made.
In Firefox, the field value starts as
"value":"0"
and therefore does not trigger this issue.The text was updated successfully, but these errors were encountered: