Proper fix for failing FileManagerDialogBrowserTest.*

chrome/browser/resources/file_manager/js/metadata_dispatcher.js

Index: chrome/browser/resources/file_manager/js/metadata_dispatcher.js
diff --git a/chrome/browser/resources/file_manager/js/metadata_dispatcher.js b/chrome/browser/resources/file_manager/js/metadata_dispatcher.js
index 8a76ae18fe674a39ac9c70b863a1c8b4f90f0827..0bad20f58a8ede701ac813a93d1add4ae2922453 100644
--- a/chrome/browser/resources/file_manager/js/metadata_dispatcher.js
+++ b/chrome/browser/resources/file_manager/js/metadata_dispatcher.js
@@ -17,11 +17,10 @@ importScripts('byte_reader.js');
  * Dispatches metadata requests to the correct parser.
  */
 function MetadataDispatcher() {
+  // Make sure to ipdate component_extension_resources.grd
+  // when adding new parsers.
   importScripts('exif_parser.js');
-  // importScripts('image_parsers.js');
-  // The line above is commented out because it caused some browser tests
-  // to fail. This is likely to be caused by crbug.com/101665.
-  // TODO(kaznacheev) wait until is gets resoved and rerun tests.
+  importScripts('image_parsers.js');
   importScripts('mpeg_parser.js');
   importScripts('id3_parser.js');