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.
Carbon: subform default TitleElement should be larger
See original GitHub issueApparently the subform titles (labels?) are not large enough to distinguish them from field titles. As far as I see right now it’s just rendering a <h5> but we might need a h4 or a h3.
@kavyanekkalapu can you please tell which one to use?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Create a form that contains a subform (a one-to-many form)
To set the Default View property of a subform: Close any open objects. In the Navigation Pane, right-click the subform and then click...
Read more >subformref (Domino DTD) - HCL Product Documentation
Represents a reference or a pointer to a subform.
Read more >Introduction to Subforms | Granicus Support
Subforms are a valuable part of Forms design due to the fact they support large numbers of functions. The key features include:.
Read more >About SubForm components
By using specific Default SubForm Spec attribute, you can specify any form to be loaded by default. The form header can be shown...
Read more >Fields :: 5.x Docs - Backpack for Laravel
AboutField types define how the admin can manipulate an entry's values. They're used by the Create and Update operations.Think of the field type...
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
Yeah, I understand. If UX confirms we need a different element, please go and change the default prop. It’s nothing truly breaking.
🎉 This issue has been resolved in version 2.20.1 🎉
The release is available on
react-form-renderer (@latest dist-tag)
pf3-component-mapper (@latest dist-tag)
pf4-component-mapper (@latest dist-tag)
mui-component-mapper (@latest dist-tag)
Demo can be found here!