Bug ID: JDK-4795485 JCK1.4a-runtime api/java_awt/interactive/FrameStateTests.html#FrameStateTests fa

Versions (Unresolved/Resolved/Fixed)

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.

Other
1.4.2_05 05Fixed

Name: icR10030			Date: 12/18/2002


Filed By       : J2SE-SQA [###@###.###
JDK            : JDK1.4.2-b10
JCK            : JCK1.4a-runtime
Platform[s]    : Solaris 8 (sparc)
switch/Mode    : -client
JCK test owner : http://javaweb.eng/jck/usr/owners.jto
Falling test[s]:
          api/java_awt/interactive/FrameStateTests.html#FrameStateTests [FrameStateTest0002, FrameStateTest0003]

JCK1.4a-runtime api/java_awt/interactive/FrameStateTests.html#FrameStateTests test fails on JDK1.4.2-b10
The bug is reproducible in GNOME 2.0 for Solaris.

Test source location:
=====================
/java/re/jck/1.4a/promoted/fcs/binaries/JCK-runtime-14a/tests/api/java_awt/interactive/FrameStateTests.java

jtr file location:
==================
/net/jtgb4u4c.sfbay/export/sail15/results/mantis/b10/jck14a/sparc/sol8_sparcclient_int_linux-1/workDir/api-interactive/java_awt/interactive/FrameStateTests_FrameStateTests.jtr

How to reproduce:
=================
1. Run the following script (you may need to change its variables)
2. Follow testcases descriptions to reproduce bug.

--- script start ---
#!/bin/bash

JCK="/net/linux-15/export/home/java/jck1.4a/JCK-runtime-14a"
JDK="/net/linux-15/export/home/java/jdk1.4.2/sparc"
switches="-Xint -Xfuture"
CLASSPATH="$JCK/classes:$JCK/lib/javatest.jar"

$JDK/bin/java $switches -cp $CLASSPATH javasoft.sqe.tests.api.java.awt.interactive.FrameState.FrameStateTests -TestCaseID FrameStateTest0002 FrameStateTest0003

--- script end ---

Test output:
============
FrameStateTest0002: Failed. Frame state test does NOT work as expected. No checkbox was selected by the user.
FrameStateTest0003: Failed. Frame state test does NOT work as expected. No checkbox was selected by the user.
STATUS:Failed.test cases: 2; all failed; first test case failure: FrameStateTest0002

Specific machine info:
======================
Hostname: linux-1
OS: Solaris 8 (sparc) + GNOME 2.0



======================================================================

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 generic tiger FIXED IN: 1.4.2_05 tiger INTEGRATED IN: 1.4.2_05 tiger tiger-b03 VERIFIED IN: 1.4.2_05

14-06-2004

EVALUATION Name: vuR10080 Date: 12/19/2002 ###@###.### 2002-12-19 This seems to be a bug in metacity, in its implementation of _NET_WM_STATE_TOGGLE. Reproducible with a simple native X11 application. Requesting XClientMessageEvent req; req.type = ClientMessage; req.window = XtWindow(toplevel); req.message_type = _XA_NET_WM_STATE; req.format = 32; req.data.l[0] = _NET_WM_STATE_TOGGLE; req.data.l[1] = _XA_NET_WM_STATE_MAXIMIZED_VERT; /* or HORZ */ req.data.l[2] = 0; will toggle full maximization, not the maximization in the specified direction only. Propose to recategorize against Gnome. ====================================================================== Name: vuR10080 Date: 12/19/2002 ###@###.### 2002-12-19 Havoc Pennington replied to my email that metacity doesn't have a concept of maximizing in only one direction, so it just takes these requests to mean maximize in both and that this is a deliberate policy decision. ====================================================================== Fix verified for build 1.4.2_05-ea-b01 Raja Dhanesh ###@###.### 2004-04-29

29-04-2004

Duplicate :	JDK-4968473 - merlin/awt/Automated/ZoomFrame tests fails in mercury
Relates :	JDK-4845535 - isFrameStateSupported does not return the correct value with Mantis on Gnome Sol
Relates :	JDK-4987087 - Frame.setExtendedState(int state) may work incorrect with misleading WM's