Bug 542108 - Wrong additional info at top of CU
Summary: Wrong additional info at top of CU
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-04 16:05 EST by Stephan Herrmann CLA
Modified: 2023-01-30 13:21 EST (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 Stephan Herrmann CLA 2018-12-04 16:05:04 EST 
Seen in the context of bug 542106:

The additional info for a delete change at the top of the file screws up around org.eclipse.jdt.internal.ui.text.correction.proposals.EditAnnotator.appendContent(IDocument, int, int, boolean) near the comment

 // no surround lines for the top no-change range

Effect: the additional info skips some lines and then shows totally unrelated content.

I believe concluding "no-change" from "startOffset == 0" is plain wrong here.
Comment 1 Stephan Herrmann CLA 2018-12-04 16:08:15 EST 
Perhaps EditAnnotator.unchangedUntil(int) should remember when deleting at 0?
Comment 2 Eclipse Genie CLA 2020-11-24 08:47:08 EST 
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.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-01-30 13:21:42 EST 
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.

--
The automated Eclipse Genie.