Please help me understand your cases, for now, I am not sure what the main goal is to add some custom HTML attributes to components. UI Builder component basically is a complex component which contains several HTML dom elements inside and has its own logic on how to render it, so injecting any HTML or JS into such a component might lead to issues.
In case you need to create a few simple components you can create your own custom components and then add any properties and handlers you need. Do you have any problems with creating components?
No, we do not have experience with HTML, it sounds like some kind of framework to build web apps. UI Builder produces a React app and in my opinion, mixing several frameworks in the same is not a good idea. Or maybe I misunderstood you, could you please provide your vision of how it might work together?
Well, the problem is, I cancelled my 14 year love affair and subscription with Webflow years ago when I decided to move full-force over to Backendless. I develop both websites and webapps using Backendless now, and hadn’t (until now) encounted problems doing what I need to do to get the job done correctly.
I think what’s happening is the Backendless JS is using the preventDefault on the native click event of an element and preventing the click event from triggering on an element with HTMX attributes on it.) …but that’s just my guess. I only use Javascript when I absolutely have to
The reason that I need to use HTMX is because I have a client that wants me to implement it, and for future flexibility.
well, we do not have onClick listeners inside the button component which might contain any prevent default
I guess it doesn’t work because this is a react app and HTML content renders in runtime while the HTMx library activates on the index.html page (which is almost empty)
All I had to do to get it to work was add the following custom code to the page’s onLoad event:
htmx.process(document.body);
Original post considered, it still would be GREAT to have the functionality of adding HTML attributes to elements within UIBuilder! (like at the end of the “Settings” heading right before “General”)