Putting the feedback section of the block interstitial to the correct place based on the mocks.

chrome/browser/resources/supervised_user_block_interstitial.js

Index: chrome/browser/resources/supervised_user_block_interstitial.js
diff --git a/chrome/browser/resources/supervised_user_block_interstitial.js b/chrome/browser/resources/supervised_user_block_interstitial.js
index e41ab19fc340136709cfc6fa01d8b6a407b1ada2..dc1532c4d06b1ed9e162cb6a928bdb4f725e75ee 100644
--- a/chrome/browser/resources/supervised_user_block_interstitial.js
+++ b/chrome/browser/resources/supervised_user_block_interstitial.js
@@ -67,11 +67,12 @@ function initialize() {
     $('request-access-button').classList.remove('hidden-on-mobile');
   };
   if (loadTimeData.getBoolean('showFeedbackLink')) {
+    $('feedback').hidden = false;
     $('feedback-link').onclick = function(event) {
       sendCommand('feedback');
     };
   } else {
-    $('feedback-link').style.display = 'none';
+    $('feedback').hidden = true;

[Bernhard Bauer, 2016/01/28 14:00:42]

Actually, do we need this if the link starts out as hidden? Alternatively, we
could do it the other way around, then the only change necessary here would be
from .style.display to .hidden.

[atanasova, 2016/01/28 14:32:57]

I went with the second suggestion, trying to keep the logic similar to what we
had before.

   }
 }