At the moment the Web Restrictions Content Provider provides an HTML error page to be displayed when a url is rejected. Although adding a Web Restrictions content provider will only be possible in a supervised user or enterprise environment, and as such in tightly controlled, it does create the potential for security holes if there are bugs in the content providers.
The only supported use of the error page is to allow supervised users of WebView to request access to URLs. In this case the content provider is always Chrome, so the plan is to move the HTML template of the error page into shared Chrome/Webview code, to replace the error message in the content provider interface with the parameters needed to build the error message, and to build the actual error message in Webview.
Comment 1 by bugdroid1@chromium.org
, Mar 18 2016