Summary
When repeatedly saving a .js file during a single session (with automatic saving turned off and without closing the Bridge app on Windows 11), the file eventually stops recording any further changes. A dot remains next to the document title in the top bar, indicating unsaved modifications. Upon closing the file, the system asks whether to save. Clicking "Yes" closes the file, but the recent edits are not preserved. This issue seems specific to the frequently used/saved .js file and can only be resolved by fully exiting and restarting the Bridge app (simply closing and reopening the file alone does not fix the issue).
To Reproduce
Open a .js file on Windows 11 with the Bridge app.
Turn off any automatic saving feature (if applicable).
Make multiple changes to the file, saving frequently in a single session using the Ctrl+S shortcut.
Occasionally press Ctrl+S twice in quick succession, potentially before the prior save process has completed.
Notice the persistent dot next to the file name in the title bar, indicating unsaved changes.
Attempt to save again; the document does not update despite indicating unsaved edits.
Close the .js file when prompted to save changes.
Observe that the document closes, but the changes are not stored.
Note that only by closing and restarting the Bridge app can the issue be resolved.
Observed behavior
After multiple saves (often triggered by Ctrl+S, sometimes in rapid succession), the .js file stops capturing changes.
Even when prompted to save upon closing, the edits do not persist.
Simply closing and reopening the file does not fix the problem; the Bridge app must be fully closed and reopened.
Expected behavior
Any new changes to the .js file should be correctly saved each time the user selects “Save,” even after multiple saves in a single session. Closing the file should properly retain all changes. There should be no need to restart the Bridge app to resume normal saving functionality.
Screenshots / File Attachments
Platform
OS: Windows 11
App Version: 2.7.45
Summary
When repeatedly saving a .js file during a single session (with automatic saving turned off and without closing the Bridge app on Windows 11), the file eventually stops recording any further changes. A dot remains next to the document title in the top bar, indicating unsaved modifications. Upon closing the file, the system asks whether to save. Clicking "Yes" closes the file, but the recent edits are not preserved. This issue seems specific to the frequently used/saved .js file and can only be resolved by fully exiting and restarting the Bridge app (simply closing and reopening the file alone does not fix the issue).
To Reproduce
Open a .js file on Windows 11 with the Bridge app.
Turn off any automatic saving feature (if applicable).
Make multiple changes to the file, saving frequently in a single session using the Ctrl+S shortcut.
Occasionally press Ctrl+S twice in quick succession, potentially before the prior save process has completed.
Notice the persistent dot next to the file name in the title bar, indicating unsaved changes.
Attempt to save again; the document does not update despite indicating unsaved edits.
Close the .js file when prompted to save changes.
Observe that the document closes, but the changes are not stored.
Note that only by closing and restarting the Bridge app can the issue be resolved.
Observed behavior
After multiple saves (often triggered by Ctrl+S, sometimes in rapid succession), the .js file stops capturing changes.
Even when prompted to save upon closing, the edits do not persist.
Simply closing and reopening the file does not fix the problem; the Bridge app must be fully closed and reopened.
Expected behavior
Any new changes to the .js file should be correctly saved each time the user selects “Save,” even after multiple saves in a single session. Closing the file should properly retain all changes. There should be no need to restart the Bridge app to resume normal saving functionality.
Screenshots / File Attachments
Platform
OS: Windows 11
App Version: 2.7.45