Why are neither src nor name props for the avatar machine?

[Oshimani]

Hi,

I find it quite peculiar that neither src nor name are being used inside the machine of the avatar component. There is a setSrc function but I can't really figure out how that would impact the src attribute when it is not managed by the machine itself.

I'd be grateful if you could share some insight on that.

https://zagjs.com/components/svelte/avatar#usage-1

[Oshimani]

 trackSrcChange({ send, scope }) {
        const imageEl = dom.getImageEl(scope)
        return observeAttributes(imageEl, {
          attributes: ["src", "srcset"],
          callback() {
            send({ type: "src.change" })
          },
        })
      },

Ok I think I found how the machine can influence the src attribute.
I still find it an odd design decision not to add src to the machine. I would imagine you would add the src attribute to the image through the api.getImageProps() function.

[segunadebayo]

This is because most users will use their frameworks' Image component, and we don't want to dictate how the image src is set. Some libraries expand the src into src and srcSet, and even add the picture element.

We'd rather not handle how images are loaded and focus on the loading lifecycle of the image/avatar instead.