Hello, I am here again. I have several ideas. 1. When I use the `a'tag, can I add a click event, open the user's default browser, and jump. 2. When I use the `img'tag, can I add a click event, preview the picture when I click and save it for download? I know these two functions can be achieved through callbacks, but there will be unnecessary trouble. Or, if you can provide a click callback, I will customize callback events when I click on a tag.

[JiangJuHong]

Hello, I am here again. I have several ideas.

1. When I use the `a'tag, can I add a click event, open the user's default browser, and jump.

2. When I use the `img'tag, can I add a click event, preview the picture when I click and save it for download?

I know these two functions can be achieved through callbacks, but there will be unnecessary trouble.

Or, if you can provide a click callback, I will customize callback events when I click on a tag.

[JiangJuHong]

The above description is not very clear, 1 and 2 is to say whether there are some built-in events when clicking, such as a tag will open the default browser, img tag can be full screen preview and download!

[JiangJuHong]

It feels similar to the render callback.

[Sub6Resources]

Thanks for the suggestions. Here are my thoughts:

A click callback is definitely on the roadmap. The callback will probably pass in the node object so that a callback implementation can read the clicked object's attributes and node tree. The callback may be added post-1.0.0 depending on what issues arise.

My thoughts on suggestions 1 and 2

1. I'm still debating whether or not to provide a built-in event for the a tag to open up the browser. At the moment, however, I'm leaning towards not adding it so as to keep the library as simple as possible from a maintenance standpoint.

2. As for the the img tag, not even a browser shows a full screen preview, so that probably will have to be programmed by you in a callback (which shouldn't be too hard since the callback will give you access to the image URL)

Sorry to cause trouble, but I'm trying to keep this library to only the bare necessities needed to display the html. After the library reaches 1.0.0, I may consider creating a wrapper plugin that adds functionality such as your suggestions.

Thanks for all your issue reports! I hope the library continues to be helpful for you.