Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Designer] Don't use placeholder for generated Inputs
See original GitHub issueVersion of SDK
latest main
Details
The designer, when you drag in most inputs (e.g. Input.ChoiceSet, Input.Text) generates elements with the placeholder property set. As we no longer want to encourage placeholders, we shouldn’t generate them by default.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Don't Use The Placeholder Attribute
Don't Use The Placeholder Attribute ... An interoperable input is created by programmatically associating a label element with it.
Read more >Form Without Labels: Don't Use The Placeholder Text!
Good news is, you can use placeholder text with any HTML input type. On the other hand, while a lot of designers and...
Read more >Placeholders in Form Fields are Harmful - input
Personally I prefer to use placeholder in input forms. Hope this standard article helps to solve your dilemma.
Read more >Placeholders are hints, not labels - Bad Habits & Enhancements
The placeholder attribute is for providing a brief hint about the expected input. It isn't very accessible and it should not be used...
Read more >Don't Use Placeholder Text as Input Field Labels — Unless...
I often see UX designers warn against using placeholder text as input field labels, and for good reason. Try typing inside the input...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@golddove got it, it makes sense. When we do this we should also have the designer set the
labelproperty to a default value.Addressing this issue is not currently on our roadmap, so closing for now. We may return to this in the future. Feel free to continue the conversation in this issue.