The “slot” feature is great and is already being used a lot in the company I work at.
After extensive use, a request to the technical team: Allow us developers to click on “edit component” even if that component is inside a slot.
More often than not, a given component only makes sense visually inside the slot that it’s in, so allowing us to click on “edit component” even if that component is inside the slot would be great.
hi @Jeandcc as developer you should not ask such request if you understand what <slot/> is. Fell free to read JS documentation or any article or tutorial about <slot/> placeholder element to understand what it is and how it works etc. There is a reason why it is mentioned in WF document related to <slot/>
@Stan , you’re a funny person… This is the second time you’ve come to one of my posts with a pessimistic view, saying something is impossible. Last time, you were proven wrong, and I custom-built the “Webflow feature” that I needed without issues… Let’s see if you have better luck this time.
Now, to the things you said:
as developer you should not ask such request if you understand what <slot/> is… ’m having a hard time unpacking all the wrong ideas and insinuations in your reply. But before making such claims, you might want to inspect Webflow’s implementation to see that they are not actually using the HTML <slot/> element. Given that Webflow is mostly an SSG tool, this should be pretty obvious. A quick inspect in the WF designer would have shown you that. Like many other features, it seems to me that Webflow just used a name that made sense, but it’s not actually using the technology that the name is known for.
If developers embraced the mindset you’re suggesting—accepting things as impossible—nothing would ever get built. Engineering is all about finding creative solutions. There’s no such thing as a truly impossible feature, just a matter of effort and ingenuity.
I totally agree with you! It would just make the workflow a bit easier.
I also disagree with @Stan . As far as I can see, the requested feature doesn’t contradict the logic of the current slot element.
Of course, WF has made this decision on purpose, but not every decision is going to lead to the best possible result. And I think it’s a good idea to post this feedback here, so that Webflow can see what our pain points are, so that they can improve the platform based on their own view and our feedbacks.
Ok guys I had a second look into WF “slot” to find that it is not a <slot/> by any means. I was surprised that it accept only “WF components”. I have set with code standard use of component template with proper*(shadowDOM)* <slot/> and tried replicate it in FW. It is absolutely different approach and different use that has absolutely nothing with slots
I presume that “no-code” creators will benefit from it but for me as old-fashioned developer it is too many abstract layers far from web standards that are well documented. Not for me.
Fell free to read JS documentation or any article or tutorial about 
