Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510513 - Inconsistencies in button bar styling between angular and non-angular screens
Summary: Inconsistencies in button bar styling between angular and non-angular screens
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: cfme-future
Assignee: Eric Winchell
QA Contact: Matouš Mojžíš
Whiteboard: ui:ownership:vm
Depends On: 1510121
TreeView+ depends on / blocked
Reported: 2017-11-07 15:20 UTC by Satoe Imaishi
Modified: 2019-04-03 03:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1510121
Last Closed:
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)

Comment 3 CFME Bot 2017-11-29 20:34:17 UTC
New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili:

commit b65eb9eeb72e67cfc8713bb54a60fdf3a28d1572
Author:     Dan Clarizio <>
AuthorDate: Mon Nov 6 10:39:37 2017 -0800
Commit:     Satoe Imaishi <>
CommitDate: Tue Nov 7 10:20:46 2017 -0500

    Merge pull request #2618 from epwinchell/form_button_cleanup1
    form button styling clean up
    (cherry picked from commit a1ddf6eab4a4d4b17b4b14780d1b30ea770e1113)

 app/assets/stylesheets/patternfly_overrides.scss   |  15 +-
 app/views/layouts/_x_dialog_buttons.html.haml      | 105 ++++----
 app/views/layouts/_x_edit_buttons.html.haml        | 264 ++++++++++-----------
 app/views/layouts/_x_form_buttons.html.haml        |   2 +-
 .../layouts/angular/_paging_div_buttons.html.haml  |   3 +-
 app/views/vm_common/_right_size.html.haml          |   2 +-
 6 files changed, 200 insertions(+), 191 deletions(-)

Note You need to log in before you can comment on or make changes to this bug.