chrome-devtools-frontend 1.0.1541169 → 1.0.1542501

package/docs/get_the_code.md

@@ -368,6 +368,15 @@ out/Default/chrome --custom-devtools-frontend=file://$(realpath out/Default/gen/
 afterwards, which can be quite a bit faster than building and linking the full
 Chromium binary.
 
+Alternatively you can use `npm start` from the DevTools sub folder (`third_party/devtools-frontend/src/`) with the browser set to `chromium`.
+This will tell the command that you are in a Chromium checkout and try to find the correct browser executable path to resolve.
+Or alternately you can use a `.env` file, see [set up here](#using-a-env-file-for-default-script-options).
+
+```bash
+cd third_party/devtools-frontend/src/
+npm start -- --browser=chromium
+```
+
 ### Testing
 
 To run the test suite, use `npm test` from within the DevTools front-end folder:

package/front_end/Tests.js

@@ -952,7 +952,12 @@
     }
 
     function gotPreferences(prefs) {
-      Main.Main.instanceForTest.createSettings(prefs);
+      Common.Settings.Settings.instance({
+        forceNew: true,
+        ...Main.Main.instanceForTest.createSettingsStorage(prefs),
+        settingRegistrations: Common.SettingRegistration.getRegisteredSettings(),
+        runSettingsMigration: false,
+      });
 
       const localSetting = Common.Settings.Settings.instance().createLocalSetting('local', undefined);
       test.assertEquals('object', typeof localSetting.get());