Bug 579154 - Invisible tab after drag and drop the windows in Eclipse 4.8 32-bit (similar to 566559)
Summary: Invisible tab after drag and drop the windows in Eclipse 4.8 32-bit (similar ...
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-08 15:15 EST by Lap Lau CLA
Modified: 2022-03-09 08:43 EST (History)
1 user (show)

See Also:

Attachments
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 Lap Lau CLA 2022-03-08 15:15:34 EST 
When dragging and dropping all the tabs outside the main application window.  if a window dragged back in, most of the outside windows were disappeared.  This is similar to bug 566559 Eclipse 4.15 (64-bit), and it fixed in 4.19.  Does the bug 566559 apply to Eclipse 4.8?  Since 4.8 is the last version of 32-bit support, can the 566559 fix backward fit to 4.8 (32-bit)?
Comment 1 Wim Jongman CLA 2022-03-09 04:55:29 EST 
(In reply to Lap Lau from comment #0)
> When dragging and dropping all the tabs outside the main application window.
> if a window dragged back in, most of the outside windows were disappeared. 
> This is similar to bug 566559 Eclipse 4.15 (64-bit), and it fixed in 4.19. 
> Does the bug 566559 apply to Eclipse 4.8?  Since 4.8 is the last version of
> 32-bit support, can the 566559 fix backward fit to 4.8 (32-bit)?

Thanks for the report Lap Lau. I am sorry but we will not backport this to 4.8. This is something you have to do yourself.
Comment 2 Lap Lau CLA 2022-03-09 08:11:56 EST 
The error that I described in Eclipse 4.8 looked similar to bug 56659 Eclipse 4.15.  Could you verify the same error exist in Eclipse 4.8?
Comment 3 Wim Jongman CLA 2022-03-09 08:43:28 EST 
(In reply to Lap Lau from comment #2)
> The error that I described in Eclipse 4.8 looked similar to bug 56659
> Eclipse 4.15.  Could you verify the same error exist in Eclipse 4.8?

That bug was also reported by you. I think you can better assess whether this is the same issue.