| Summary: | [CoolBar] Reparenting of item controls does not work | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> | ||||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | tbuschto | ||||||
| Version: | 1.3 | ||||||||
| Target Milestone: | 1.3 M2 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ralf Sternberg
Created attachment 144381 [details]
Snippet to reproduce
The same snippet works as expected in SWT.
The problem is that disposing of a CoolItem also disposes of the control that is set on this item (since qooxdoo diposes of children recursively). A solution might be to set the parent of _control to null in the CoolItem.js#destruct method, i.e. just before disposing of the item. However, I tried this and I got a different Javascript error... We need to check how reparenting works in qooxdoo. Created attachment 144404 [details]
Patch to outline a possible approach
This patch does not solve the whole problem but we must not forget t o add these lines...
Tim, is this bug fixed as part of bug 237268 ? The snippet works fine for me with or without patch 145259. This is also what i actually would expect, since widgets are disposed on the client using "destruct", not "dispose". ( "destruct" does not dispose the children. ) Marking as FIXED. |