Bug 4530

Summary: failed to issue an invalidParent error in XtMakeResizeRequest-3
Product: Xtests Reporter: Rui Feng <fengrui>
Component: XTSAssignee: Stuart Anderson <anderson>
Status: RESOLVED MOVED QA Contact: Xorg testing team <xorg-test>
Severity: normal    
Priority: high CC: fengrui
Version: unspecified   
Hardware: x86 (IA32)   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: proposed patch for xc/lib/Xt/Geometry.c
proposed patch for Xt8/tmkrsizrt.m

Description Rui Feng 2005-09-21 02:39:47 UTC 
XtMakeResizeRequest-3 failed to issue an invalidParent error and
XtMakeResizeRequest-4 failed to issue an invalidGeometryManager error. The
reason comes from two ways:
1. in xc/lib/Xt/Geometry.c
   it disables the error of invalidParent and invalidGeometryManager 
   since many applications and toolkits (including parts of Xaw, 
   motif and Netscape) depend on the previous Xt behaviour.
 
   so we have to enable it for these two cases, which is related to
   both XtMakeResizeRequest-3 and XtMakeResizeRequest-4.
 
2. in the test case of XtMakeResizeRequest-3
   XtVaCreateWidget should be replaced by XtVaCreateManagedWidget
Comment 1 Rui Feng 2005-09-21 02:44:31 UTC 
Created attachment 3341 [details] [review]
proposed patch for xc/lib/Xt/Geometry.c
Comment 2 Rui Feng 2005-09-21 02:45:24 UTC 
Created attachment 3342 [details] [review]
proposed patch for Xt8/tmkrsizrt.m
Comment 3 chemtech 2013-03-15 13:49:18 UTC 
Rui Feng,
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 4 GitLab Migration User 2018-08-10 21:43:42 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/test/xts/issues/17.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.