Editing Client ID immediately after saving Scope results in UI issues

Steps to reproduce:

1. Add a new OAuth 2 Application
2. Navigate to Scopes tab within the application form
3. Enable any scope and save
4. Navigate back to the Credentials tab
5. Click the pencil icon to the right of the Client ID field
6. Click the Apply button within the popup modal

Expected result:
The Client ID field values within the Edit Client ID modal is applied to the Client ID field in the main form and the modal closes.

Actual result:
The modal value is applied to the main form, however the modal fails to close and the following error shows up in the browser console:

Uncaught TypeError: component.simulate is not a function
at_com_liferay_oauth2_provider_web_internal_portlet_OAuth2AdminPortlet_updateComponent (<anonymous>:54:64)

Subsequent changes to the Client ID field would reproduce this issue including changes to any other OAuth 2 application, even ones where there original changes were not made.

Note:
This is reproducible with the Edit Client Secret modal as well. A workaround is to navigate away from the OAuth 2 Administration portlet entirely (e.g. navigate to portal home page) and back to the form. You would still see the issue if you navigate away from the form to the main OAuth 2 Administration page and back to the form.

Reproduced on:
Portal master Git SHA: fe0b18c6515960e5a1d4dbad3475ebd9606d16ab
Portal 7.1.x Git SHA: f5130602000d4eefb2d855fdff5e9de437439cc8