HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


Problem Report 1684 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1684.


Report 1684 Actions


    Problem Report Number 1684
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0057
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-07-17 08:00
    Expiry Date 1999-07-17
    Product Standard X Window System Display
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.1
    Test Identification Xlib4/XCreateWindow 29, 41
    Problem Summary MSF4W.00023 This implementation has visual types which it does not distinguish as these tests require.
    Problem Text
    Failing Testcases:

    XCreateWindow 29 41
    XChangeWindowAttributes 31 43
    XSetWindowColormap 2

    All of the above expect BadMatch errors to be generated as a result
    of operations where two conflicting visuals are in use. In our case
    we have a number of visuals which differ only in visualid.
    i.e. class is the same, rgb masks are the same, bits_per_rgb is the
    same and map_entries is the same.


    We request a temporary waiver due to the minimal impact caused by
    this problem.
    Test Output
    TEST CASE: XCreateWindow

    TEST PURPOSE #29
    Assertion XCreateWindow-29.(A)
    When colormap and the window do not have the same visual
    type, then a BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create colour map of different visual to window.
    METH: Attempt to set colourmap to created colour map.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    29 FAIL

    TEST PURPOSE #41
    Assertion XCreateWindow-41.(A)
    When colormap is CopyFromParent and the window does not
    have the same visual type as the parent window, then a
    BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create a parent of one visual type
    METH: Attempt to set colourmap to CopyFromParent on window of different v
    isual type.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    41 FAIL

    TEST CASE: XChangeWindowAttributes

    TEST PURPOSE #31
    Assertion XChangeWindowAttributes-31.(A)
    When colormap and the window do not have the same visual
    type, then a BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create colour map of different visual to window.
    METH: Attempt to set colourmap to created colour map.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    31 FAIL

    TEST PURPOSE #43
    Assertion XChangeWindowAttributes-43.(A)
    When colormap is CopyFromParent and the window does not
    have the same visual type as the parent window, then a
    BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create a parent of one visual type
    METH: Attempt to set colourmap to CopyFromParent on window of different v
    isual type.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    43 FAIL


    TEST CASE: XSetWindowColormap

    TEST PURPOSE #2
    Assertion XSetWindowColormap-2.(C)
    If more than one type of visual is supported: When the
    colormap argument does not have the same visual type as the
    window specified by the window argument w, then a BadMatch
    error occurs.
    METH: For each supported visual:
    METH: Create a colormap not of that visual type.
    METH: Create a window of that visual type.
    METH: Verify that a call to XSetWindowColormap generates a BadMatch error.

    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    2 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend a Temporary Waiver for a minor system fault be granted. We
    believe the impact on application portability will be negligable.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Minor System Fault (MSF)
    Review Conclusion
    A Temporary Waiver is granted.

    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority