Moon compiler does not apply DOM event listeners or attributes to created element by for about moon HOT 4 CLOSED

Hey!

Thanks for the detailed testing and bug reports by the way, it really helps :)

for takes a data prop as an object which it will apply as data, and it doesn't apply DOM properties with ...props or something similar to avoid unexpected behavior.

Try something like:

<for={entry} of={data.list} name="ul" data={{
   id: "test-id",
   "@click": dec
}}></for>

I've considered DOM fragments before, but came across issues with the logic to remove them from the DOM. There is no equivalent of fragment.parentNode.removeChild(fragment) AFAIK. That's why I went with the custom parent element options route. Let me know what you think.

from moon.

Wonderful! I have verified this gives the intended behavior. Although, I found this to be surprising from an API standpoint.

I can see why fragments would complicate dom operations.

from moon.

Awesome! It can be a little surprising, but I personally think that it's better than having conflicts with other DOM property names. For example, you wouldn't be able to set a name attribute on an element because it it used for the name of the element instead.

from moon.

Closing as it works as documented — let me know if you have any suggestions to change the API.

from moon.