HTML Attributes vs. DOM Properties

Re:HTML Attributes vs. DOM Properties by berkes on Thursday April 25, 2024 @06:25AM (#40155655)

For primitive types, serde isn't hard. It could even be part of a simple spec. Numbers, Dates, String[], Number[], Date[]. Edit: Or it could just be JSON.

For complex types it is. But why and when do you need to store complex types in the DOM? Isn't that always a bad idea?

I'm a seasoned web dev, but haven't been working on complex frontend apps, because I believe complexity and frontend web don't go together. So I may very well miss some use-cases.

[ Parent | on HN ]

Re:HTML Attributes vs. DOM Properties by bryancoxwell on Thursday April 25, 2024 @06:52AM (#40155848)

For custom elements you may want to store data or methods that modify the element’s behavior.

[ Parent | on HN ]

Re:HTML Attributes vs. DOM Properties by berkes on Thursday April 25, 2024 @11:23AM (#40158656)

Methods as in callbacks? So, code? Do you then store a closure or such? Or a pointer to one (i.e. the function/name)? And how or what data would modify behaviour?

As said: I'm unfamiliar with these concepts as I actively try to avoid them :)

[ Parent | on HN ]