Bug 262431 - IFileModificationValidator.validateEdit not called when spelling quick fix performed
Summary: IFileModificationValidator.validateEdit not called when spelling quick fix pe...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-26 16:00 EST by Kevin Sawicki CLA
Modified: 2019-09-06 16:07 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Sawicki CLA 2009-01-26 16:00:06 EST 
IFileModificationValidator.validateEdit not called when spelling quick fix is performed from a tooltip activated by F2 in the Java source editor.

Steps to reproduce:
- Create a project that is under control of a RepositoryProvider that returns a IFileModificationValidator from getFileModificationValidator
- Enable spell checking in Eclipse
- Open a Java file in the Java Editor from that project
- Put a typo in a Javadoc comment so a spelling squiggle appears
- Close and re-open the editor
- Hover over the spelling squiggle
- Hit F2
- Select a spelling correction ("Change to XXXX")

Outcome:
Editor is marked as dirty although IFileModificationValidator.validateEdit is not called

Expected Outcome:
IFileModificationValidator.validateEdit would be called before the editor is marked as dirty.

This affects team plugins that need to checkout files before an edit occurs.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:07:14 EDT 
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.