-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardize header, footer, and content language #22092
Milestone
Comments
I vote for "body" (which is semantically similar to table markup: <thead>,<tbody>, & <tfoot>) |
+1 body |
mdo
added a commit
that referenced
this issue
Jun 15, 2017
Part of an update to align the naming schemes across our components. - Renames .popover-title to .popover-header - Renames .popover-content to .popover-body Refs: #22092
This was referenced Jun 15, 2017
mdo
added a commit
that referenced
this issue
Jun 15, 2017
Part of an update to align the naming schemes across our components. - Renames .popover-title to .popover-header - Renames .popover-content to .popover-body Refs: #22092
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is not a standard with how bootstrap refers to the header, footer, and content of an element. There are at least 4 items which fall into this category:
tooltip-inner
modal-header
modal-body
modal-footer
card-header
card-block
card-footer
popover-title
popover-content
For the most part the header and footer format is the same, but the content section seems to be on a per component basis. I would suggest standardizing the language around these sections to improve discoverability. If a user who has used cards before tries to use a modal, the first things they will try is
modal-header
,modal-block
,modal-footer
since that is what they used for card. Currently only 2 out of 3 of those will work. I think everyone would agree that a discoverable API is a very important part of a successful service and drastically improves ease of use.The text was updated successfully, but these errors were encountered: