-
Bug
-
Resolution: Fixed
-
P4
-
7, 9
-
b68
-
generic
-
os_x
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8098717 | emb-9 | Alexandr Scherbatiy | P4 | Resolved | Fixed | team |
http://java.net/jira/browse/MACOSX_PORT-385 submitted 2011/09/09 by Yuri Nesterenko
There is an optional feature of the Frame setMaximizedBounds(Rectangle). It does override a system-provided rectangle for the Frame, when maximized. It is optional in a sense that a platform may not honor it at all or use only size and/or not location of the user-supplied Rectangle. For instance, Apple JDK 6 and MS Windows does use all of the Rectangle; Gnome totally ignores location; Xfce ignores everything.
As of now (September) Mac Port does ignore this hint. Perhaps we even should consider it a regression from jdk 6.
I'm attaching a trivial example file for convenience.
There is an optional feature of the Frame setMaximizedBounds(Rectangle). It does override a system-provided rectangle for the Frame, when maximized. It is optional in a sense that a platform may not honor it at all or use only size and/or not location of the user-supplied Rectangle. For instance, Apple JDK 6 and MS Windows does use all of the Rectangle; Gnome totally ignores location; Xfce ignores everything.
As of now (September) Mac Port does ignore this hint. Perhaps we even should consider it a regression from jdk 6.
I'm attaching a trivial example file for convenience.
- backported by
-
JDK-8098717 [macosx] setMaximizedBounds() should be implemented
-
- Resolved
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Resolved
-