Client Side JavaScript for User Data #3129
Unanswered
radleylewis
asked this question in
Q&A
Replies: 1 comment 1 reply
-
you can execute any amount of Javascript on the client side so Htmx doesn't have any conflicts with that. If you want to modify the DOM, people usually use AlpineJS to add interactivity to pages without having to do a roundtrip to the server, such as toggling a css class. If your goal is to be able to perform DOM replacements with htmx without having to go to the server that's not supported "out-of-the-box" but I guess you could use a service worker to intercept request and return the proper html in response. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question
With the growth of htmx our team is interested in developing part of our product with it! We are developing a Web3 application whereby the user will require that some code is executed only in the browser. I am wondering if this approach with htmx (where most code is executed on the server) is acceptable or anyone has experience with such a structure.
For context, the vast majority of the application would be using standard htmx convention, but some JavaScript would need to be bundled and served/executed in the browser as it pertains to the user sensitive information and decrypted/encrypted data.
Beta Was this translation helpful? Give feedback.
All reactions