Ticket #2528264 (checkedin enhancement)
Reporter Peter Abrahamsen |
Opened: 09/22/09 Last modified: 02/6/10 Status: checkedin Type: enhancement Resolution: fixed |
Owner  Satyen Desai |
Target Release: 3.1.0 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Widget should support a parentNode attribute | ||
| Description: | A 'parentNode' attribute, specified on Widget or one of its subclasses, could be used to ensure that all widgets were created within a particular portion of the document. I'm happy to hear suggestions of other ways of ensuring this behaviour. |
||
| Type: | enhancement | Observed in Version: | development master |
| Component: | Widget | Severity: | S4 (low) |
| Assigned To: | Satyen Desai | Target Release: | 3.1.0 |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 10/12/09
|
|
Posted: 02/6/10
Added DEF_PARENT_NODE property to allow component developers to over-ride default behavior of rendering to BODY if no parent node or existing markup is provided. Fixes #2528264 |
Users can pass a node to render() to control where the widget is placed in the document.
Currently the default parent node if a node is not passed to render() is the body element of the document which contains the bounding box.
I can see value in allowing users to customize this default.