Bug 121915 - [DnD] Lower right trim items overlaid by window resize icon on Mac OS X
Summary: [DnD] Lower right trim items overlaid by window resize icon on Mac OS X
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-22 14:21 EST by Sean Montgomery CLA
Modified: 2019-09-06 15:37 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Montgomery CLA 2005-12-22 14:21:30 EST
Using 3.2M4 on Mac OS X 10.4.3, enable showing of Heap Status via preferences. Have it dock on the bottom.  On my machine this places the Heap Status "trim" on the lower right of the window.  Note that the OS X window resize icon, in the lower right of any resizable window, overlays the Heap Status "trim".

Any "trim" that can be placed on the bottom of an Eclipse window should be kept from being overlaid by the OS X resize icon.
Comment 1 Kim Horne CLA 2006-01-03 09:58:42 EST
This is a general issue with trim items on OS X.
Comment 2 Sean Montgomery CLA 2006-04-02 21:44:21 EDT
Yup, Kim's right, it's all over the place in 3.2M6.  It's even in the resizeable Content Assist popup.  I take it that 3.2M6 implements Content Assist via the new PopupDialog architecture mentioned in bug 72374 - does that code rely on Platform UI to prevent text from overwriting the resize icon, or should I create a new bug for that case?
Comment 3 Eric Moffatt CLA 2007-06-21 14:08:04 EDT
McQ suggests that we could change the layout to adjust its right edge to leave room for the spacer...
Comment 4 Eclipse Webmaster CLA 2007-07-29 09:18:41 EDT
Changing OS from Mac OS to Mac OS X as per bug 185991
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:37:23 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.