UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2756.0 Safari/537.36

Steps to reproduce the problem:
1. Enable the experimental flags for material design and specifically the material design extensions flag.
2. Trigger an extension error. The settings menu icon will change from grey dots to orange, and when clicked, an "Extension Error" notice will clearly appear at the top, leading to chrome://extensions when clicked.
3. On loading chrome://extensions, no notice or other information about the extension error will appear. 

What is the expected behavior?
When material design is *not* enabled and the old chrome://extensions page is shown, the extension responsible for the error will have a red background and brief information about the error.

What went wrong?
Nothing is shown related to the error on chrome://extensions with material design enabled.

Did this work before? N/A 

Chrome version: 53.0.2756.0  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

Since material design is still in development, one assumes the display of extension errors simply hasn't been written for it yet. Presumably the relevant developers haven't experienced an extension error while working on the material design code and thus haven't been reminded that it needs to be written.

I noticed it because one of my extensions always throws a harmless error on starting Chrome - I go to chrome://extensions, de- and re-enable it, and go on browsing. On trying out the material design experiment, I noticed the error was shown in the settings menu, but not on the MD chrome://extensions. It's definitely still happening, it's just not being shown on chrome://extensions.