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
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Make some edits in Brackets -- don't save your changes yet
Leave Brackets and modify (or delete) the same file on disk
Return to Brackets -- you'll get a prompt about keeping your editor changes vs. refreshing from disk
Put your finger on the computer screen where the destructive button is (the 'lose editor changes' button)
Click the other button to keep your changes for now... but keep your finger in place
Switch to a different app, but leave the Brackets window uncovered
Move the mouse to where your finger is, and click in the Brackets window
Result: your editor changes have been blown away without warning
This happens because the window gains activation on mousedown, and the dialog appears... and then the mouseup triggers the button in the dialog.
Note that these long repro steps are needed only to reliably hit the bug. You could hit this by accident -- by clicking in an unlucky spot -- just by doing steps 1,2,7.
In theory, any asynchronous process that spawns a popup dialog without user interaction could have this same issue. So hopefully there's a generic solution for this we can put into Dialog.
The text was updated successfully, but these errors were encountered:
Nominating for 1.0 -- although we don't hear complaints about this often (other than causing some confusion during testing in Sprint 35), the prospect of data loss is real and fixing it should be easy.
@peterflynn I can't reproduce this any more on Win - The dialog can be easily seen while the window is inactive (but uncovered).
Are you sure that's still a problem?
Result: your editor changes have been blown away without warning
This happens because the window gains activation on mousedown, and the dialog appears... and then the mouseup triggers the button in the dialog.
Note that these long repro steps are needed only to reliably hit the bug. You could hit this by accident -- by clicking in an unlucky spot -- just by doing steps 1,2,7.
In theory, any asynchronous process that spawns a popup dialog without user interaction could have this same issue. So hopefully there's a generic solution for this we can put into Dialog.
The text was updated successfully, but these errors were encountered: