-
Bug
-
Resolution: Fixed
-
P4
-
jfx25
-
master
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8364275 | jfx25.0.1 | Michael Strauß | P4 | Resolved | Fixed | master |
| JDK-8364142 | jfx25 | Michael Strauß | P4 | Resolved | Fixed | master |
In an extended stage, developers can choose between default window buttons or custom window buttons.
For default window buttons, the visibility should match what would be expected for the OS. On Windows, disabled buttons are greyed out but visible; with GNOME and KDE, disabled buttons are invisible.
For custom window buttons, only the disabled state is set by JavaFX; the visible state is left to the purview of application developers.
For default window buttons, the visibility should match what would be expected for the OS. On Windows, disabled buttons are greyed out but visible; with GNOME and KDE, disabled buttons are invisible.
For custom window buttons, only the disabled state is set by JavaFX; the visible state is left to the purview of application developers.
- backported by
-
JDK-8364142 Fix window button states of an extended stage
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8313424 JavaFX controls in the title bar (Preview)
-
- Resolved
-
- links to
-
Commit(jfx25)
openjdk/jfx/5398b14c
-
Commit(master)
openjdk/jfx/bc433da8
-
Review(jfx25)
openjdk/jfx/1855
-
Review(master)
openjdk/jfx/1831
(2 links to)