As part of Bug 32067 - [OMNIBUS] Consistent classes for submit and/or primary buttons: This patch will update buttons in the Acquisitions area so that buttons which are currently styled as primary buttons will have the the "btn btn-primary" classes. In some places, the classes have been added to buttons which were not input[type='submit'] but which should be styled as primary.
Created attachment 142925 [details] [review] Bug 32070: Consistent classes for primary buttons: Acquisitions This patch makes changes the button markup in Acquisitions templates so that all submit buttons and any buttons that should should be styled as primary buttons have the Bootstrap class "btn btn-primary." To test, apply the patch and view pages in Acquisitions to confirm that everything looks correct. In most cases there are no visible changes.
Looking here...
Created attachment 142954 [details] [review] Bug 32070: Consistent classes for primary buttons: Acquisitions This patch makes changes the button markup in Acquisitions templates so that all submit buttons and any buttons that should should be styled as primary buttons have the Bootstrap class "btn btn-primary." To test, apply the patch and view pages in Acquisitions to confirm that everything looks correct. In most cases there are no visible changes. Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 142987 [details] [review] Bug 32070: Consistent classes for primary buttons: Acquisitions This patch makes changes the button markup in Acquisitions templates so that all submit buttons and any buttons that should should be styled as primary buttons have the Bootstrap class "btn btn-primary." To test, apply the patch and view pages in Acquisitions to confirm that everything looks correct. In most cases there are no visible changes. Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Passing QA as this just improves markup consistency.. What I'm less sure about is having all the actions buttons on the closed basketgroups table be primary.. it feels like primary should be saved for 'the main action on a page'.. can we really have a whole table full of 'main actions'? One for the new style guide I reckon.
I agree. I simply applied classes according to the existing markup, which consisted of input[type='submit'] which would have had the primary appearance regardless of the added class.
Pushed to master for 22.11. Nice work everyone, thanks!