Thanks guys, after updating and a hard refresh it is now working as expected!
2 Likes
Just started testing this component; thanks! Iād curious about adding Placeholder text to private messages. Has anyone tried that?
Private messages have the same default placeholder text as Topic posts. It can be changed by the site administrators under the admin settings Customize > Text. Search for js.composer.reply_placeholder - as shown at the top of this thread.
If you use this component to customise the placeholder text for each Topic Category, the default placeholder text should only apply to the Private Messages.
1 Like
This theme component is really cool. Iāve been trying to find a way to give my users a little more guidance when they create a topic, and would like to make the experience more like completing a form.
Right now, this theme component makes it so that all text that is preloaded in a topic is a single placeholder. So, once a user types anything in the topic composer, all of the placeholder text goes away.
Would it be possible to have it so that there are different placeholders on the page? For example, the topic template could load a separate placeholder for:
āNameā
āLocationā
āIssueā
So that when the users types in their name, the other placeholders for Location and Issue stay there, until the user types in their spots too?
The default Discourse Topic Template Text stays whilst the user is typing. It sounds like that is what you need?
The Placeholder Approach:
What I (and others?) would be looking for would behave more like placeholders in a form (meaning with separate form elements).
The basic default behavior now would allow me to list out different sections of the form, like what I wrote (ānameā, ālocationā, and āissueā), but the default template behavior has the same problems as noted beforeāmarkdown makes it confusing and user can break it easily.
I think the ideal would be like a normal form, where there is a placeholder for each section (name, location, and issue), but (hereās the difference) the sections would behave independently. So when the user clicks on the name section, the placeholder ānameā disappears, but the other sections stay until the user clicks on those too.
I could imagine this being possible (?) with jquery. Each section would have to have its own div with id, and then jquery would allow showing or removing the text of that particular id when the user clicks on it. This would require adding divs into the textarea, however, and Iām not sure how to do that.
Iām investigating that here.
The Template Approach
Probably an alternative would be that the section headers donāt ādisappearā when the user clicks. So the section headers (example: Name, Location, and Issue) would be text that would stay on the page. To make it more form-like, compared to the current template default:
- The section header text could not be edited by the user (ie,
contenteditable="false") - The section break points could not be removed by the user
- There would be space below the section header where itās clear the user can type. In the current default template, theyād have to go to where the text is, hit
return, to create space to type.
Perhaps this is the easier way to do it?
I found this setting only apply on first post not working.
It doesnāt work if I want all posts in a topic have the same placeholder and deactivate the setting. I get a standard placeholder in this case.
Any possibility of having a placeholder specific to replies (not the first post in a topic)? Iām hoping to give users more guidance on what can be in a reply, and a placeholder that pops up in a reply would be helpful.
4 Likes
Iāve found that this works for replies only if the placeholder text has more than one line. Got no idea why as the code is a bit too complicated for me.
P.S.
While there Iāve dropped in a small PR to stop the browser console warnings:
https://github.com/naidihr/discourse-topic-template-placeholders/pull/8
1 Like
Merged thank you Nathan.
2 Likes