On Thu, 8 Dec 2022 05:03:45 GMT, Tejesh R <t...@openjdk.org> wrote:

>> Why we cannot make inaccessible JFileChooser same as JFrame? We do not need 
>> to mark disable all components inside the frame(I guess jdialog and windows 
>> as well). Both are top level components, and probably should work in the 
>> same way.
>
> I guess for frame, the disable/enable functionality is handled by the peer 
> (Windows it is `WFramePeer`), whereas for the swing components it should be 
> the components itself like it is for all other components (Like in 
> AbstractButton, JComboBox, JList).

The JFileChooser is also kind of top level component and it has the peer. 
Current patch does not work as intended. On macOS in Nimbus/Metal L&F the list 
of files looks disabled but scrolling works. On Aqua L&F the list of files does 
not look like disabled, accept scroll and double clicks, but does not accept 
single clicks.

-------------

PR: https://git.openjdk.org/jdk/pull/11553

Reply via email to