[MD Settings][People] Disables profile name field for legacy supervised users.

chrome/test/data/webui/settings/people_page_manage_profile_test.js

Index: chrome/test/data/webui/settings/people_page_manage_profile_test.js
diff --git a/chrome/test/data/webui/settings/people_page_manage_profile_test.js b/chrome/test/data/webui/settings/people_page_manage_profile_test.js
index 6d9fd3e2310ba13527820a26915d8a14f9930b1a..6b43927ce7006fd44c5b1487be2242834753e792 100644
--- a/chrome/test/data/webui/settings/people_page_manage_profile_test.js
+++ b/chrome/test/data/webui/settings/people_page_manage_profile_test.js
@@ -43,6 +43,7 @@ cr.define('settings_people_page_manage_profile', function() {
         manageProfile = document.createElement('settings-manage-profile');
         manageProfile.profileIconUrl = 'fake-icon-1.png';
         manageProfile.profileName = 'Initial Fake Name';
+        manageProfile.syncStatus = {supervisedUser: true, childUser: false};
         document.body.appendChild(manageProfile);
       });
 
@@ -96,6 +97,9 @@ cr.define('settings_people_page_manage_profile', function() {
 
         assertEquals('Initial Fake Name', nameField.value);
 
+        // Name field should be disabled for legacy supervised users.
+        assertTrue(!!nameField.disabled);

[tommycli, 2016/10/03 20:37:22]

Can we separate out the legacy supervised users into a separate test?

Otherwise this test simulataneously tests: 1. That the field is disabled and 2.
Changing the field and firing a change event...

It just seems... kind of schizophrenic to have the same test do both :D

[Moe, 2016/10/03 22:26:43]

fair enough! done.

+
         nameField.value = 'New Name';
         nameField.fire('change');