JDK-6195928 : REG: Fully functional FileDialog is not shown when security manager is installed, on win32
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-11-16
  • Updated: 2010-04-02
  • Resolved: 2005-06-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b15Fixed
Related Reports
Relates :  
Description
I am printing a frame through AWT PrintJob. I have set the dialog type to Native and I have installed a Security Manager. I have given the following permissions though Policytool:

RuntimePermission - QueuePrintJob
RuntimePermission - SetSecurityManager
FilePermission - ALL FILES - ALL PERMISSIONS

I am running the application on WinXP on Tiger/Mustang. Native PrintDialog comes up. I am selecting PrintToFile checkbox and clicking 'OK'. On 1.4.2, a normal, fully functional file dialog appears. But on Tiger/ Mustang, only a textfield appears in the file dialog (similar to the file dialogs that were appearing on 1.3) thereby preventing the user from using other functionalities of the file dialog such as Dir creation, file rename, navigation through dirs etc. This is incorrect.

This is reproducible only on WinXP, since Tiger. Not reproducible on 1.4.2. 

I have attached a sample test. Execute the sample test. Security Manager will be installed by default. Click on Native Dialog button. A native dialog would appear. Click on 'PrintToFile' option and click OK. If a dialog appears with a single textfield and a couple of buttons, the bug is reproduced.

###@###.### 2004-11-16 15:23:28 GMT

Comments
EVALUATION Fix for 5065001 in mustang-b15 also fixed this bug. Marking as integrated. ###@###.### 2005-06-01 17:32:08 GMT
01-06-2005