Content
View differences
Updated by Florian Kraft almost 11 years ago
**As** a developer
**I want** that buttons in plugins are styled in the same way as in the core,
**so that** changes to the core styles are also reflected on plugin buttons.
### Acceptance criteria
- change usages of `styled_submit_tag` (or `submit_tag`) to `styled_button_tag`)
- change usages of `f.submit` to `f.button` (you can’t use `::before` pseudo-selectors on `<input>` tags)
- apply relevant icon modifiers, e.g. `-success -with-icon icon-yes`
### Note on sub-stories
I tried to only include plugins as substory, that add buttons and therefore will need a re-styling. However, I was not always sure if a certain plugin touches buttons. Therefore I created sub stories wherever I assumed buttons to be touched by the plugin.
**tl; dr:** Some sub-stories might be resolved by not changing any code.
**I want** that buttons in plugins are styled in the same way as in the core,
**so that** changes to the core styles are also reflected on plugin buttons.
### Acceptance criteria
- change usages of `styled_submit_tag` (or `submit_tag`) to `styled_button_tag`)
- change usages of `f.submit` to `f.button` (you can’t use `::before` pseudo-selectors on `<input>` tags)
- apply relevant icon modifiers, e.g. `-success -with-icon icon-yes`
### Note on sub-stories
I tried to only include plugins as substory, that add buttons and therefore will need a re-styling. However, I was not always sure if a certain plugin touches buttons. Therefore I created sub stories wherever I assumed buttons to be touched by the plugin.
**tl; dr:** Some sub-stories might be resolved by not changing any code.