Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351219 - [syntax highlighting] syntax coloring unstable with @link that spans multiple lines
Summary: [syntax highlighting] syntax coloring unstable with @link that spans multiple...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 12:15 EDT by Markus Keller CLA
Modified: 2020-03-13 17:17 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-07-05 12:15:05 EDT
BETA_JAVA7

Semantic highlighting is unstable for the first inline @link tag in the example below.

I have the "Javadoc > Links" element type set to italics. The first @link toggles between italic and upright, but I'm not 100% clear what conditions cause the toggling. The second @link tag is stable.

Holding Ctrl down and moving the mouse onto the first "deepEquals" usually makes the link upright.

After changing the target of Mark Occurrences, the link is usually italic again.


package snippet;

import java.util.Arrays;

/**
 * The algorithm in {@link Arrays#deepEquals(Object[],
 * Object[]) Arrays.deepEquals} is used to determine equality.
 * <p>
 * Single line:
 * {@link Arrays#deepEquals(Object[], Object[]) Arrays.deepEquals}
 */
public final class Objects2 {
}
Comment 1 Markus Keller CLA 2011-07-05 12:28:30 EDT
Same problem in 3.5.2.

Bug 104379 is about missing highlighting of the second line (which i still see in 3.7).
Comment 2 Dani Megert CLA 2013-06-17 05:42:46 EDT
Funny bug.
Comment 3 Eclipse Genie CLA 2020-03-13 17:17:35 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.