Findings in test session (17.12.2024)

[fedejeanne]

Objective

• Find bugs when rescaling at runtime is active

Setup

• Tested on the I-BUILD I20241216-1800: https://download.eclipse.org/eclipse/downloads/drops4/I20241216-1800/download.php?dropFile=eclipse-SDK-I20241216-1800-win32-x86_64.zip

Raw findings

These findings need to be processed an turned into proper tickets.

Federico

• Primary 100% left, Secondary 175% right

1. Start Eclipse in 100% monitor and change the zoom to 175% -> looks odd (Screenshot)
2. Create very long method, hover over the method in the outline view so that the name of the method is displayed in a tooltip that crosses over to the monitor on the right --> milk screen (Screenshot)
3. Window stretching over both monitors, 51% on the left (100%), open "Command palette" with Ctrl+3 --> The palette opens on the right monitor and it is full-screen
4. Preferences: Text and Buttons

• Open the Preferences > Editor > Save Actions
• Change DPIs around, both of the current monitor and the other one --> The UI refreshes and the size changes but buttons and other UI elements look Odd. Probably related to @ShahzaibIbrahim's
  issue nr. "S2"

5. Help in preferences (unrelated to scaling / Edge): Image
   • Open Window > Preferences and click on the "Import" button --> Dialog opens.
   • Click on the "Help" button --> Nothing happens

Edge

1. Welcome page can't navigate back:
   -Open the welcome page > Tutorials > "Create a Hello World application" --> It navigates to a new page.

   • Click on "Restore Welcome" --> It doesn't go back
   • This is NOT reproducible on my Eclipse IDE (Build id: I20241216-1800)

2. JavaDoc: Video

   • Start Eclipse on 175% secondary monitor
   • Hover over a class to show its JavaDoc and move the mouse into it --> it vanishes
     Open a JavaDoc

3. Help doesn't show, only a tooltip

   • Workbench on 175% monitor (right)
   • Press F1 to open the help
   • Go to "Search" and click on the "Default" (Scope) --> Dialog opens
   • Click on the "Help" button --> Tooltip open on the left (100%) monitor. It should have opened the help page (HTML) on the right side of the dialog.

Marty

Configuration: Right (Primary) 100%, Left 175 %, left to left 100%

• The ide on right, drag the editor out and hover at the edge where left and left to left meet, there's a jump in the rectangle (Fixed by using the multi zoom coordinate system mapper)
  

• Tooltip scales to the monitor zoom instead of shell zoom #175
  

• Toolitems Images Cutoff on dragging to the vertical toolbar #178
  

• Min/Max button not scaled correctly when an editor is dragged out and placed in 100% monitor and also when it is attached back. #176
  

• Context Menu image size is based on the shell size #177
  

• Button scaling not done wrt the content inside: start refactor > move on 175 and move to 100, the scaling is bad
  dragging an editor from 175% to 100% creates scaled up editor
  

Shahzaib

S1) Moving from Secondary (200) to Primary (150) Project -> Properties -> Save actions. the text area is not scaling ( also with project -> properties -> Clean Up)
#168
S2) Moving from Secondary (200) to Primary (150) Project -> Properties -> Save actions. buttons (text scaling but not the button layout)
#165

S3) Moving from Secondary (200) to Primary (150) Help - > Show Context Help -> Images not scaled or aligned

#169
S4) On 200% monitor. When removing the conditional breakpoint, the dialog has a message for "Do not show this message again" cutoff. (Checked only in dark theme for now)
#170

[fedejeanne]

@amartya4256 , @ShahzaibIbrahim , @akoch-yatta please update your issues properly if necessary and add the screenshots to them too.

[HeikoKlare]

Have individual issues already been created for all the findings? Otherwise we should probably convert all the finding in issues and link the issues here to see that everything is covered by a dedicated issue.

[ShahzaibIbrahim]

@HeikoKlare I have linked mine

[fedejeanne]

Tip: If you add the "[ ]" to the items (in edit mode) then you can Convert them to issues

[HeikoKlare]

@fedejeanne are your findings already documented in explicit issues?