Opened 14 years ago

Closed 13 years ago

Last modified 12 years ago

#474 closed defect (fixed)

ContentPane script deficiencies / cleanup problems

Reported by: bill Owned by: mumme
Priority: high Milestone:
Component: Widgets Version: 0.2
Keywords: Cc:
Blocked By: Blocking:

Description

Bugs related to specifying <script> tags in URL passed to ContentPane? setUrl().

  1. setUrl() to reset the content of a content pane will delete all the widgets currently in the content pane, but it won't cleanup where the current content had <script>dojo.event.connect(...)</script>.

At the least, need some kind of hook so the content can clean up after itself.

  1. ContentPane? can contain 2 types of <script>. A dojo.require() call must be executed before the widgets are instantiated, but other <script> stuff should be executed after the widgets have been instantiated. Need some way to allow this.

Change History (6)

comment:1 Changed 13 years ago by Tom Trenka

Milestone: 0.3release0.4

comment:2 Changed 13 years ago by bill

Owner: changed from bill to mumme

Fredrik has implemented some of this stuff but I guess it's still in progress. Assigning bug to him

comment:3 Changed 13 years ago by mumme@…

Owner: changed from mumme to anonymous
Status: newassigned

I did implement these things, I am however a bit uncertain if the cleanup part is working, leaving this bug open for a while to hear if there is any issues.

More info about the executeScript thing in this document http://dojotoolkit.org/~mumme/scriptScope.pdf

/ Fredrik

comment:4 Changed 13 years ago by mumme@…

Owner: changed from anonymous to mumme
Status: assignednew

comment:5 Changed 13 years ago by mumme

Resolution: fixed
Status: newclosed

As this bug is resolved since 0.3 (enhanced in 0.3.1) and there insnt that many complaints about memleak related to scriptScope, Im closing this bug.

If there still is issues with the cleanup part there will probably be a new ticket anyway.

comment:6 Changed 12 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.