UIHandler: Event delegation, introducing DOM handleEvent *) #400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have no ambition to "fix" anything, I am giving purely for consideration/discussion a modification that has worked well for me in an AJX-heavy / custom elements riddled application.
handleEvent
to rule them all), no manual binding, no unreachable bound methods.ajax
selector, but with something likenaja.uiHandler.selector = ':not([data-naja="off"])'
— completely different situation.)removeEventListener('click', naja.uiHandler)
. If you need to.BC Break: The
bindUI
function has been removed as there is no further use for it.*) Since 2000; see: https://dom.spec.whatwg.org/#interface-eventtarget