JDialog content is offset underneath the title bar when using "apple.awt.documentModalSheet"

[Paul Taylor]

On 19/03/2013 20:38, Christopher Brown wrote:
> Hello again Anthony,
>
> More generally, with regard to the various Apple-specific client properties
> for Swing, is there a reference document listing which ones are planned to
> be (or already are) supported in the Oracle / OpenJDK implementation?  I
> assumed it could be on the project status page but couldn't find it.
>
> I certainly hope as many as possible will be supported, I found the
> technique was a clean way to provide extra platform-specific polish without
> going against cross-platform compatibility.  I would be interested in
> testing them out (which is why I wondered if there's a reference document,
> to avoid indicating bugs with features that may have been dropped).
>
> Thanks,
> Christopher
>
Christioper

I think they are all there in the current development release build 
1.7.0_12-ea-b08

Paul
> On 18 March 2013 14:24, Anthony Petrov <anthony.petrov at oracle.com> wrote:
>
>> Hi Christopher,
>>
>> This looks like an issue in Oracle JDK. I filed a bug for you:
>> http://bugs.sun.com/view_bug.**do?bug_id=8010197<http://bugs.sun.com/view_bug.do?bug_id=8010197>
>> (should be available in a day or two).
>>
>> --
>> best regards,
>> Anthony
>>
>>
>> On 03/17/13 02:01, Christopher Brown wrote:
>>
>>> Hello,
>>>
>>> When using the Swing client property "apple.awt.documentModalSheet" on JDK
>>> 1.7.0_17 on a Mountain Lion Retina MacBook Pro, the dialog is the expected
>>> size but the content is offset (moved up under the title bar) and
>>> hidden/clipped.  When this property is not set, the layout is as expected.
>>>
>>> The "sheet" dialog behavior is not present as it was in Apple JDK 6.  I
>>> don't know if it is planned to fully implement it.  However, it appears
>>> that this property is still taken into account by Oracle JDK 7 to offset
>>> the content, but because the title bar's still there, it leads to layout
>>> issues.
>>>
>>> I didn't find any reference to this issue on the bug database or by
>>> searching on the Internet.  Is this the correct place to raise the issue?
>>>
>>> Thanks,
>>> Christopher
>>>