Layout nits for the signin email confirmation dialog.

chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js

Index: chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js
diff --git a/chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js b/chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js
index ef2ebbc8018e3d40bda7a594785f5192db20cd6b..0a78974153765bdfabdd3f713b27a9fde5927f43 100644
--- a/chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js
+++ b/chrome/browser/resources/signin/signin_email_confirmation/signin_email_confirmation.js
@@ -11,9 +11,9 @@ cr.define('signin.emailConfirmation', function() {
     var newEmail = args.newEmail;
     $('dialogTitle').textContent = loadTimeData.getStringF(
         'signinEmailConfirmationTitle', lastEmail);
-    $('createNewUserRadioButton').innerHTML = loadTimeData.getStringF(
+    $('createNewUserRadioButtonTitle').innerHTML = loadTimeData.getStringF(

[Dan Beam, 2017/01/11 18:56:02]

could this be .textContent instead?

[msarda, 2017/01/12 16:11:07]

Not, this cannot be .textContent as this contains HTML (the value of the string
is "<strong>This wasn't me.</strong> Create a new profile for xxx@gmail.com")

[Dan Beam, 2017/01/12 18:32:58]

please use I18nBehavior and i18n() or i18nAdvanced() instead then (or
parseHtmlSubset directly). innerHTML can cause security issues. I just reviewed
a sandbox bypass fix where innerHTML was part of the exploit chain.

[msarda, 2017/01/13 09:54:16]

Done.

         'signinEmailConfirmationCreateProfileButtonTitle', newEmail);
-    $('startSyncRadioButton').innerHTML = loadTimeData.getStringF(
+    $('startSyncRadioButtonTitle').innerHTML = loadTimeData.getStringF(
         'signinEmailConfirmationStartSyncButtonTitle', newEmail);
 
     document.addEventListener('keydown', onKeyDown);