JDK-8068905 : Disabling Java Plug-in/Enable the next-generation Java Plug-in does not disable security tab radio buttons
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 7u76
- Priority: P3
- Status: Closed
- Resolution: Not an Issue
- OS: windows
- Submitted: 2015-01-13
- Updated: 2015-02-28
- Resolved: 2015-02-07
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.
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 7 | JDK 8 | JDK 9 |
|---|---|---|
7u79Fixed  |
8u40Resolved |
9Resolved |
Description
In the Java control panel, prior to 7u76, when 'Java Plug-in/Enable the next-generation Java Plug-in' setting is disabled, the 'Security tab' slider for Security level selection gets greyed out. 7u76 onwards, the Security tab contains radio buttons for Security level selection instead of slider. But, the disabling of 'Java Plug-in/Enable the next-generation Java Plug-in' checkbox does not disable the security level selection radio buttons. The radio buttons remains selectable. Testsuite name: JDF common Test name(s): AdvancedTabTest::testAdvancedJavaPluginDisableCheckLevelDescription Product(s) tested: 7u76b13 OS/architecture: Windows x64-32 Reproducible: Always Is it a Regression: Not sure Prior to 7u76, the Security tab has slider. From 7u76, instead of slider there are radio buttons. So this could be an issue introduced as part of this change. Is it a platform specific issue: Yes (Windows) Steps to reproduce: (Please refer to the screenshots attached)
Comments
|