<AWT Dev> [8] Review request for 8025225: Window.setAlwaysOnTop documentation should be updated

[Artem Ananiev]

On 9/27/2013 6:04 PM, Alexander Zvegintsev wrote:
> Hi Anthony, Artem,
>
> Here is updated webrev:
>
> http://cr.openjdk.java.net/~serb/alexz/8025225/webrev.01/

Looks good (I'm not a native speaker, though).

Thanks,

Artem

> Thanks,
>
> Alexander.
>
> On 09/26/2013 05:22 PM, Artem Ananiev wrote:
>>
>> On 9/24/2013 2:06 PM, Anthony Petrov wrote:
>>> Hi Alexander,
>>>
>>> I suggest to mention that a call to setAlwaysOnTop(false) may also cause
>>> an unspecified, platform-dependent change in the z-order of top-level
>>> windows (still respecting their always-on-top states, however).
>>> Otherwise this isn't clear from the current spec.
>>
>> +1
>>
>> Thanks,
>>
>> Artem
>>
>>> --
>>> best regards,
>>> Anthony
>>>
>>> On 09/24/2013 01:34 PM, Alexander Zvegintsev wrote:
>>>> Hello,
>>>>
>>>> Please review the fix for the issue:
>>>> https://bugs.openjdk.java.net/browse/JDK-8025225
>>>> The webrev is available here:
>>>> http://cr.openjdk.java.net/~serb/alexz/8025225/webrev.00/
>>>>
>>>> This issue was raised by Metacity's specific behavior:
>>>> If we have two windows(#1 has always-on-top state and has no window
>>>> focus and #2 has window focus),
>>>> then calling setAlwaysOnTop(false) on #1 will bring #2 window to front
>>>> of #1.
>>>>
>>>> This fix makes more space for such window manager behavior.
>>>>
>>>>> The window remains in the top-most position
>>>> Previous version of javadoc also does not cover a case when an another
>>>> always-on-top window presented.
>>>>
>>>> CCC request will be send after dev's review.
>>>>
>