Bug 537201 - JavaDoc preview doesn't escape type parameter, leading to underline
Summary: JavaDoc preview doesn't escape type parameter, leading to underline
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-07-19 14:41 EDT by Jeff Brower CLA
Modified: 2022-09-15 11:47 EDT (History)
0 users

See Also:

Attachments
Image displaying javadoc preview. (22.73 KB, image/png)
2018-07-19 14:41 EDT, Jeff Brower CLA 		no flags Details
View All 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 Jeff Brower CLA 2018-07-19 14:41:15 EDT 
Created attachment 275056 [details]
Image displaying javadoc preview.

When hovering over the javadoc preview for a class with a type argument of U, the preview appears to render an HTML <U> tag, causing the rest of the javadoc entry to be underlined. See the attached image.

I suspect the same issue would arise for other tag names, such as <I> and <B>.
Comment 1 Eclipse Genie CLA 2020-08-29 16:54:46 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.

--
The automated Eclipse Genie.
Comment 2 Noopur Gupta CLA 2020-08-31 07:07:37 EDT 
Can you provide a sample code here to reproduce the issues?
Comment 3 Eclipse Genie CLA 2022-09-15 11:47:41 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.

--
The automated Eclipse Genie.