Ticket #8046 (closed bug: wontfix)
$().find() triggers DOMSubTreeModified events
|Reported by:||judson@…||Owned by:|
I've been building a library to make packaging behaviors simple. It works very well against jQuery 1.4.2. However, the Sizzle included in 1.4.3 and 1.4.4 uses a technique to keep track of it's place in the DOM - it changes the id of nodes as it traverses. In 1.4.3, it's about line 3904 of the unmini'd version.
When the id changes (at least in Chrome) a DOMSubtreeModified event gets thrown. The trouble is, I've attached a handler to the document for DSM events that needs to find the target Element - which triggers a DSM.
Is it reasonable for $().find(selector) to trigger an event?
- Priority changed from undecided to low
- Resolution set to wontfix
- Status changed from new to closed
- Component changed from unfiled to selector