Bug? hx-on:* not fired when using hx-trigger="load"

[michal-laskowski]

This will not work

  it('before-request - without delay', function() {
    var requests = 0
    window.foo = 0
    this.server.respondWith('GET', '/test', function(xhr) {
      requests++
      xhr.respond(200, {}, 'Requests: ' + requests)
    })
    var div = make('<div hx-trigger="load, click" hx-get="/test" hx-on:htmx:before-request="window.foo += 1">Requests: 0</div>')
    div.innerHTML.should.equal('Requests: 0')
    this.server.respond()
    div.innerHTML.should.equal('Requests: 1')
    div.click()
    this.server.respond()
    div.innerHTML.should.equal('Requests: 2')
    delete window.foo
    window.foo.should.equal(2)
  })

When usind delay:1 it will work.

  it('before-request - with delay', function(done) {
    var requests = 0
    window.foo = 0
    this.server.respondWith('GET', '/test', function(xhr) {
      requests++
      xhr.respond(200, {}, 'Requests: ' + requests)
    })
    var div = make('<div hx-trigger="load delay:1ms" hx-get="/test" hx-on:htmx:before-request="window.foo += 1">Requests: 0</div>')
    div.innerHTML.should.equal('Requests: 0')
    this.server.autoRespond = true
    this.server.autoRespondAfter = 5

    setTimeout(function() {
      window.foo.should.equal(1)
      delete window.foo
      div.innerHTML.should.equal('Requests: 1')
      done()
    }, 50)
  })

[rkilpadi]

I found similar issues with reveal and intersect. Looks like this bug happens when triggers fire before the node is fully processed (see addTriggerHandler()). hx-on attributes are processed after the rest of the node (see processNode()) and therefore don't have a chance to attach before these triggers fire.

Edit: Nevermind this next part, I can't get inheritance to work on triggers at all, if this is a bug it is a separate issue.

I also found issues with inheritance for all these triggers when invoking hx-on attributes.
The following works as intended and increments foo only when the div is not immediately revealed:

<div hx-trigger="revealed" hx-get="/test" hx-on::before-request="foo++"></div>

However, the following doesn't increment foo in either case:

<div hx-trigger="revealed">
    <div hx-get="/test" hx-on::before-request="foo++"></div>
</div>

Replacing revealed with load delay:1ms has similar results.

I wonder if hx-on processing logic could/should be rewritten so that it can happen within initNode() to prevent some of these issues.