Opened 11 years ago

Closed 8 years ago

#8486 closed enhancement (wontfix)

dojo.parse/reparse to improve support for ASP.net Ajax pages

Reported by: Matt Walsh Owned by: bill
Priority: high Milestone: future
Component: Parser Version: 1.2.3
Keywords: Cc:
Blocked By: Blocking:

Description

Due to the way asp.net pages generate 'garbage' ids on its controls and the asp.net ajax panel behavior, its very annoyingly difficult to properly destroy just the right set of dijits before an ajax postback. To be safe you have to dijit destroy everything and reparse everything, and IE7 is not "speedy" re-doing its DOM on every postback.

working suggestion

-- add a callback hook for dojo.parse collision handling instead of just throwing and exception

-- by default the base dojo callback hook just throws as usual

-- implement dojo.reparse( domNode, callback ) so that the older collision dijit can be cleaned up by a custom callback function

Change History (2)

comment:1 Changed 11 years ago by dante

Milestone: tbdfuture

moving tbd's -> future for 1.3b1

comment:2 Changed 8 years ago by bill

Resolution: wontfix
Status: newclosed

I think you could do this yourself by using advice around dijit/registry's add() method. I don't see a need to add any code to the parser for it.

Note: See TracTickets for help on using tickets.