Will you please implement srcset already?

Support
#1

Please tell us that v6 will have this srcset built into the image element. I’ve been following the latest release with great interest and the stuff you guys are doing is unbelievable and waaaay better than anything out there – by lightyears. Seriously, bravo on everything so far. That’s why it’s so baffling that this is still a thing. You have solved much bugger problems to provide the tools and UI advancements you have in this system over the years.

Please don’t repeat that the dev team has it in the issue tracker and how there are complexities that have prevented it from being done in previous versions. While there are certainly complexities with this, we’ve already heard all that because most of us have been following this forum topic since 2019 and before when this was first brought up as a gaping hole in the image element. That hole is still here. And we are still waiting to be able to provide the kinds of image optimizations our clients expect from us.

Even if it meant that I had to manually configure images I wanted to add to the set and at what sizes they should be invoked (as opposed to some sort of automated process derived from Wordpress’ native support for this feature), I would gladly do it that way. Hell, that might even be sold as a feature, tbh. As it stands in this system, that’s really what I have to do with the html in a raw content element anyway – a process I have not implemented on a large scale in projects because I’ve been holding my breath for this feature to appear inside the image element natively, as it should.

Please get this thing done. This is too awesome of a platform to not have this very essential feature built in.

#2

Hey @simeoned,

You might not like my response as I’m going to post your feedback in our issue tracker so our development team will see it when they will review the tracker.

I’m also going to add this as a feature request.

Thank you for your feedback and understanding.

#4

Well, @christian, it’s not what I had hoped to hear…

Like I say, I could imagine a section of the image element with something functioning like an ACF repeater where we can add an additional source after the main one and tell those sources when they should be loaded. That would bring us into sane territory with tooling for mobile vs. desktop experiences.

For now, I’ve been trying to figure out something that could be done in the mean time…
I even started to try and experiment with adding custom attributes to an image to see if I could get a work around going that way but… I see that there is a span wrapper around the img element and the attributes are actually added to that, not the img element itself. Which means I could not really go down that road either.

Which brings up a good point. When adding custom attributes to an element, if that element is going to have wrappers added to the output, shouldn’t we have the option of assigning those attributes to the html we desire and not just the wrapper?

To be clear, I see why a wrapper is applied in general. I don’t see why the custom attribute is applied to it rather than the img itself. If I wanted to do that, I’d have to do some DOM manipulation and that isn’t ideal for the application I am imagining.

#5

Hey @simeoned,

Like I said,

Thank you for your feedback. I’ll add that as a feature request.

For now, there is nothing we can do in this case except you use the Raw Content element and insert your own
HTML structure.

If you’re expecting custom codes to alter the elements, that’s not possible.

Thank you for understanding.

#7

No, this is not what I am expecting you to provide…

When I said:

I was saying the image element needs an upgrade and I was describing the kind of enhancements I could imagine being useful for this purpose. The expectation I do have is that the dev team does something to address this ongoing issue (which has real user demand in this community) in some reasonable amount of time. But it need not be what I have imagined and described specifically. Those guys know what they’re doing and could imagine a much more elegant solution I’m sure. Just want to make it clear that this is nontrivial to the people using your platform and the clients we build sites for.

#8

Hey @simeoned,

I personally hear you, and that is why I previously said I added your feedback to my issue tracker report but you said it’s not what you hoped to hear.

My feature request report will surely be read by our development team.

Please kindly wait.

Thank you.