lighthouse 9.5.0-dev.20230104 → 9.5.0-dev.20230106

package/core/config/constants.js

@@ -110,6 +110,7 @@ const defaultSettings = {
   disableStorageReset: false,
   debugNavigation: false,
   channel: 'node',
+  usePassiveGathering: false,
   skipAboutBlank: false,
   blankPage: 'about:blank',
 

package/core/user-flow.js

@@ -73,8 +73,13 @@ class UserFlow {
    */
   _getNextFlags(flags) {
     const clonedFlowFlags = this._options?.flags && deepClone(this._options?.flags);
-    if (!flags) return clonedFlowFlags;
-    return mergeConfigFragment(clonedFlowFlags || {}, flags, true);
+    const mergedFlags = mergeConfigFragment(clonedFlowFlags || {}, flags || {}, true);
+
+    if (mergedFlags.usePassiveGathering === undefined) {
+      mergedFlags.usePassiveGathering = true;
+    }
+
+    return mergedFlags;
   }
 
   /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "lighthouse",
   "type": "module",
-  "version": "9.5.0-dev.20230104",
+  "version": "9.5.0-dev.20230106",
   "description": "Automated auditing, performance metrics, and best practices for the web.",
   "main": "./core/index.js",
   "bin": {

package/types/lhr/settings.d.ts

@@ -73,6 +73,8 @@ export type ScreenEmulationSettings = {
   debugNavigation?: boolean;
   /** If set to true, will skip the initial navigation to about:blank. This option is ignored when using the legacy navigation runner. */
   skipAboutBlank?: boolean;
+  /** If set to true, gatherers should avoid any behavior that may be destructive to the page state. (e.g. extra navigations, resizing the viewport) */
+  usePassiveGathering?: boolean;
 
   /** How Lighthouse should interpret this run in regards to scoring performance metrics and skipping mobile-only tests in desktop. Must be set even if throttling/emulation is being applied outside of Lighthouse. */
   formFactor?: 'mobile'|'desktop';