Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #18702
Closed
Open
Issue created Dec 27, 2015 by Administrator@rootContributor

v4: Specify how the validation cases should be used

Created by: tordans

I don't understand the difference between danger and warning and the documentation gives no suggestions about when to use what.

The way I understand forms they have a default style and an error style. I do understand the success style for cases where you have inline validation. But what are the use cases or usage szenarios for danger and warning?

Suggestions:

  • Add a sentence or two about when to use danger and when to use warning – the decision should not be a visual but a semantic one, so what is the semantic?
  • Ideally: Link to some blog post or book that describes having those two cases as separate styles as a best practice from a user / usability point of few. My go to guy for web form best practices is LukeW. He wrote about best practices for inline validations http://alistapart.com/article/inline-validation-in-web-forms and he wrote a book an many presentations about form in general (http://static.lukew.com/webforms_lukew.pdf and http://www.lukew.com/resources/web_form_design.asp). Unfortunately for bootstrap, there is no indication that it even makes sense to have a warning and danger as two separate indicators. So maybe this is something that should be reduced to one in version 5?

This is the part I am referring to: http://v4-alpha.getbootstrap.com/components/forms/#validation

Validation Bootstrap includes validation styles for danger, warning, and success states on form controls. To use, add .has-warning, .has-danger, or .has-success to the parent element. Any .form-control-label, .form-control, and .text-help within that element will receive the validation styles.

Assignee
Assign to
Time tracking