Community
Participate
Working Groups
HEAD but also 3.6.1 1. Open a new workspace 2. Import Team Project Set from bug 340666, attachment 191685 [details] 3. Select the 2 projects, choose Compare With > Each Other 4. Open a difference, e.g. .classpath 5. Edit the file on left => Editor becomes dirty (good). 6. Try to Undo => Nothing happens (bad). => Actually, if you're fast enough, you should be able to undo the change but the editor will be still dirty (bad, I'm not sure which case is worse).
(In reply to comment #0) > => Actually, if you're fast enough, you should be able to undo the change but > the editor will be still dirty (bad, I'm not sure which case is worse). In many cases the editor stays dirty even if you undo the change (with Ctrl+Z, I assume). Mainly for those when saving is not made by our component but is custom-handled. I understand handling dirty state on undo properly is much better, but it's not so uncommon that you are requested to save file if you have been modifying it even if you reverted all your changes. But, of cause, I don't deny this one is a bug: > => Nothing happens (bad).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
