From c44f49ef94cd17af66fb5ef3f3cb6535c40c1a68 Mon Sep 17 00:00:00 2001
From: Ken Dreyer <kdreyer@redhat.com>
Date: Dec 02 2019 12:15:18 +0000
Subject: swap "Add" and "Cancel" button ordering for access management


Prior to this change, the "Cancel" button was much too close to the
place where users click to select an access level. This made it too easy
for users to accidentally click the "Cancel" button after quickly
clicking on all the other interface choices.

Move the "Add" button to the left so that it is directly below the
dropdown input field.

Merges https://pagure.io/pagure/pull-request/4665

---

diff --git a/pagure/templates/add_group_project.html b/pagure/templates/add_group_project.html
index e69d19e..0fdd20e 100644
--- a/pagure/templates/add_group_project.html
+++ b/pagure/templates/add_group_project.html
@@ -36,8 +36,8 @@
       </fieldset>
 
       <p class="buttons indent">
-        <input type="button" value="Cancel" class="btn btn-secondary cancel_btn">
         <input type="submit" class="btn btn-primary" id="add_update_button" value="Add">
+        <input type="button" value="Cancel" class="btn btn-secondary cancel_btn">
         {{ form.csrf_token }}
       </p>
     </form>
diff --git a/pagure/templates/add_user.html b/pagure/templates/add_user.html
index a4bd4e8..e5acd4a 100644
--- a/pagure/templates/add_user.html
+++ b/pagure/templates/add_user.html
@@ -34,8 +34,8 @@
       </fieldset>
 
       <p class="buttons indent">
-        <input type="button" value="Cancel" class="btn btn-secondary cancel_btn">
         <input type="submit" class="btn btn-primary" id="add_update_button" value="Add">
+        <input type="button" value="Cancel" class="btn btn-secondary cancel_btn">
         {{ form.csrf_token }}
       </p>
     </form>