#1238484: Ability to mark the form buttons to be of a specific type (so that they can be styled differently)
#1167350: Action links were ignored
#1719640: Use 'button' element instead of empty links
- There are various button CSS styles throughout core, which duplicate each other and are not semantic classes in the first place.
- Remove duplicate CSS.
- Simplify CSS.
- Semantic classes.
- Follow common web design standards.
- Form #type 'submit' (
- Form #type 'button' (
- Form #type 'image_button' (
- Menu action links (
- Links styled as buttons.
a.button(links as buttons)
- Remove element names from CSS selectors.
- End up with:
- Wherever anyone needs or wants a properly styled button, just use and apply
Discuss and decide
.button— Tons of CSS in the wild uses the abbreviated class name
Bootstrap is just a single of plethora of examples. Even though we generally do not abbreviate strings in Drupal, perhaps it would make sense to follow that very common class name, so as to make it easier to use a theme framework?
I'm aware that Foundation uses
.button, but I've seen plenty of random themes, jQuery plugins, and front-end libraries that use
Image buttons are only mentioned in the above for completeness. We probably do not want to touch those and keep them explicitly separate, since an image button shouldn't get styled like any other button, as it presents a custom visual element already.
@ry5n thankfully adjusted those to
- Part of this essentially means to move Button Style module into Drupal core.