JDK-6658876 : TitledBorder API inconsitent with implementation: uses TOP instead of DEFAULT_POSITION
- Type: Bug
- Component: client-libs
- Sub-Component: javax.swing
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2008-02-04
- Updated: 2011-02-16
- Resolved: 2010-05-21
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 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
The API for TitledBorder is inconsistent with its implementation. The API for the DEFAULT_POSITION static states: "Use the default vertical orientation for the title text." However, the actual implementation defaults to a hardcoded value of TOP instead of DEFAULT_POSITION when a position is not specified. Among the side effects of this is that the Nimbus LAF cannot correctly specify a different default position other than TOP. Ideally, the implementation would be brought into conformance with the spec, and the default text position would be DEFAULT_POSITION.
Comments
|