Bug 571911 - [quick diff] Don't copy diff tokens from popup when hovering a diff annotations
Summary: [quick diff] Don't copy diff tokens from popup when hovering a diff annotations
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.18   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-12 04:25 EST by Lukas Eder CLA
Modified: 2023-03-14 10:51 EDT (History)
1 user (show)

See Also:


Attachments
This is what I see when hovering a quick diff annotation (20.39 KB, image/png)
2021-03-12 04:25 EST, Lukas Eder CLA
no flags Details
This is what I see when I select the contents. I don't want to select the + > - tokens (23.44 KB, image/png)
2021-03-12 04:26 EST, Lukas Eder CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Eder CLA 2021-03-12 04:25:47 EST
Created attachment 285819 [details]
This is what I see when hovering a quick diff annotation

When hovering a quick diff diff annotation, a useful popup appears showing the diff. It usually contains some diff tokens showing what was added/removed/modified, e.g.

> 
-         /**
-          * Corresponds to {@link Connection#createStatement()} and
-          * {@link Statement#executeBatch()}
-          */
-         BATCH


While seeing those tokens (e.g. + > -) is probably useful, I really never want to copy them from the popup. It would be great if they weren't part of the selectable text, see screenshots
Comment 1 Lukas Eder CLA 2021-03-12 04:26:16 EST
Created attachment 285820 [details]
This is what I see when I select the contents. I don't want to select the + > - tokens
Comment 2 Kalyan Prasad Tatavarthi CLA 2021-03-18 05:46:50 EDT
Quick Diff is provided by org.eclipse.ui.editors plugin, so moving to Platform UI.
Comment 3 Eclipse Genie CLA 2023-03-14 10:51:44 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.