You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is blank areas appearing in the UI on Mac 14 (Sonoma). See #1012
This affects macOS 14 (Sonoma) and whether the target launcher binary is linked to Mac SDK 14. The target launcher binary can be java in the case of running a child Eclipse or RCP app instance, or eclipse when running Eclipse itself.
As of now the eclipse launcher binary is linked to Mac SDK 13 so this issue won't manifest when running Eclipse (or an RCP app) itself. However, it may be that one day the eclipse binary will be linked to Mac SDK 14. See eclipse-equinox/equinox#495
Temurin JDK 17.0.10, 21.0.2 and later versions are linked to Mac SDK 14 so the issue will be seen when launching a child Eclipse instance that targets one of these JDKs, because the binary launcher in this case is java.
Background
The problem is blank areas appearing in the UI on Mac 14 (Sonoma). See #1012
This affects macOS 14 (Sonoma) and whether the target launcher binary is linked to Mac SDK 14. The target launcher binary can be
java
in the case of running a child Eclipse or RCP app instance, oreclipse
when running Eclipse itself.As of now the
eclipse
launcher binary is linked to Mac SDK 13 so this issue won't manifest when running Eclipse (or an RCP app) itself. However, it may be that one day theeclipse
binary will be linked to Mac SDK 14. See eclipse-equinox/equinox#495Temurin JDK 17.0.10, 21.0.2 and later versions are linked to Mac SDK 14 so the issue will be seen when launching a child Eclipse instance that targets one of these JDKs, because the binary launcher in this case is
java
.Current remedy
The solution is to set
setClipsToBounds
to true for anNSView
. See https://developer.apple.com/documentation/macos-release-notes/appkit-release-notes-for-macos-14#NSViewThis has been done in three places in two PRs in the
Widget
component. See #1081 and #1232Long-term remedy
Those three instances of
setClipsToBounds
may not be enough and ideally we should set it just once in the constructor ofNSView
like this:However, this is not as simple as inserting one line of code as explained by @lshanmug - #1081 (comment) and I'll quote it here:
So I've opened this issue to track the possibility of doing this. Disclaimer - I don't know how to do this, so help required!
The text was updated successfully, but these errors were encountered: