On Fri, 17 Apr 2026 20:12:47 GMT, Phil Race <[email protected]> wrote:
>> It has been noted that the java.awt.FileDialog specification could be >> clearer that the UI showing a file as selected to load/open is not just >> variable in how it is done, the platform might not do it at all, and since >> FileDialog is (usually) a completely native component, we can only reinforce >> the platform is what decides if this is possible. >> >> The CSR is ready for review. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Phil Race has updated the pull request incrementally with two additional > commits since the last revision: > > - 8381843 > - 8381843 src/java.desktop/share/classes/java/awt/FileDialog.java line 532: > 530: * It is also platform-specific as to what happens for {@code LOAD} > mode of a non-existent file. > 531: * For example, it may be possible for the user to "accept" the > {@code setFile} value or > 532: * to edit in the name some other file to load/open even if it is > not present. "in the name **of** some" Also, this sentence is not coming out perfect to me, maybe "it may be possible.....to edit a non-existent file to load/open" is maybe more simpler.. src/java.desktop/share/classes/java/awt/FileDialog.java line 553: > 551: * <p> > 552: * Multiple mode may be ignored in some cases, for example commonly > 553: * {@code SAVE} mode dialogs do not support it. commonly -> usually ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30777#discussion_r3186070020 PR Review Comment: https://git.openjdk.org/jdk/pull/30777#discussion_r3186071727
