Not sure whether this should be technically classified as a bug or feature request.
When a text property has been assigned to a component and that property has been connected to the content of a block, and when no text has been typed for it, it will be great to show the placeholder text in the component as well as in the Component inspector.
Step-by-step reproduction instructions:
Open the Post Editor/Site Editor
Create a component (with an instance in the navigator)
Add a text property to it with a placeholder and leave the property value empty for the instance
Add a heading
Connect the text property to the heading’s content
Notice that the placeholder is not used for the heading’s display “A Heading.” is shown instead.
This is not a bug as not intended, but I can definitely see the use of this, although a field placeholder might hold a different role compared to a block content placeholder.
Would love to know what others think about this (I already see multiple likes on here).
@Louis, Given the fact that a major feature highlight is that you have made component properties as easily editable from the editor canvas as from the properties inspector panel, adding this just makes a lot of sense.
If we want the component itself on the canvas to have the same usability hints as the property panel, then we need to be able to show the placeholder there.
As mentioned in another thread, I’d be grateful if we can keep thread contexts clear and relative to their initial subject, which is not the case with your last post.
Components do support dynamic text. Please open a new thread accordingly and I will reply there.
