http://gwt-code-reviews.appspot.com/623803/diff/1/4 File user/src/com/google/gwt/dom/client/DOMImplTrident.java (right):
http://gwt-code-reviews.appspot.com/623803/diff/1/4#newcode161 user/src/com/google/gwt/dom/client/DOMImplTrident.java:161: // TODO: Hang on to enough information to implement dispose() properly. On 2010/07/02 16:26:08, tbroyer wrote:
I guess the implementation would be pretty similar to the
DOMImplStandard one
re. setFn/getFn, just that setFn would probably also push on a Map<EventTarget,Set<EventListener>> (or use an expando on the
EventTarget) which
would be used by dispose()
In other words, maybe setFn/getFn should be instance methods
(non-static) at the
DOMImpl level, with DOMImplTrident overriding setFn as explained
above. That makes perfect sense to me. I just wanted to get the standard implementation working first. And Trident is going to require extra bookkeeping to allow dispose() to work properly (if only you could enumerate extant event handlers... sigh.). http://gwt-code-reviews.appspot.com/623803/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
