Hide the edit/add buttons for fields the user can't update

Currently the /registrar-settings backend endpoint will fail to update any
OWNER fields that a non-OWNER tries to change.

However, the front-end (soy, js) still allow non-OWNERs to try and change
these fields (there's the "edit" or "add" button, and it only fails when you try to "save")

This CL changes the front-end to remove the ability for non-OWNERs to even try
and change these fields. However, it will still let them *view* these fields as
it has interesting and important information.

-------------------------------

In addition - it changes the webdriver tests to include the "edit buttons". Those were never tested before, and now we will test to see if they are indeed displayed or not.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=223845883
This commit is contained in:
guyben 2018-12-03 12:51:37 -08:00 committed by jianglai
parent f980a25b32
commit a3a60075a0
19 changed files with 118 additions and 74 deletions

View file

@ -196,13 +196,10 @@ li.kd-menulistitem {
}
.kd-appbar {
padding: 0.75em 0;
}
#reg-app-buttons {
/* Same as in reg-content below. Lines the left edge of the
appbuttons and content area with the 'R' in Registry. */
/* same as in reg-content below. lines the left edge of the
appbuttons and content area with the 'r' in registry. */
padding-left: 173px;
padding-top: .75em;
}
.kd-content-sidebar {
@ -214,7 +211,7 @@ li.kd-menulistitem {
#reg-nav {
position: fixed;
left: 0;
top: 128px;
top: 136px;
width: 155px;
margin: 0 25px 0 0;
z-index: 3;
@ -261,7 +258,7 @@ li.kd-menulistitem {
#reg-content-and-footer {
position: absolute;
top: 105px;
top: 136px;
left: 173px;
bottom: 0;
width: 100%;