Bug 551762 - Javadoc image overscaling
Summary: Javadoc image overscaling
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.13   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-04 04:51 EDT by Pierre-Yves Bigourdan CLA
Modified: 2023-09-16 12:38 EDT (History)
0 users

See Also:


Attachments
Javadoc hover overscaling (110.48 KB, image/png)
2019-10-04 04:51 EDT, Pierre-Yves Bigourdan CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Yves Bigourdan CLA 2019-10-04 04:51:56 EDT
Created attachment 280158 [details]
Javadoc hover overscaling

I'm currently working with the Spring Webflux framework. Most of the reactive APIs documentation contain explanatory SVG images, however, they appear as significantly overscaled in Eclipse.

See the attached screenshot for an example in the Javadoc hover: only about a quarter of the image is visible. Even when using the Javadoc view, significant screen space has to be allocated to avoid having to constantly be scrolling.

Note that I've been able to reproduce this on both macOS with a 2280*1800 display and Windows with a 1360*768 display.
Comment 1 Eclipse Genie CLA 2021-09-24 05:40:53 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 Eclipse Genie CLA 2023-09-16 12:38:03 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.