Skip to content

Conversation

@adamraine
Copy link
Contributor

So we can avoid weird audit skip logic in user flows #14465 (comment)

Will help with #14336

@adamraine adamraine requested a review from a team as a code owner December 13, 2022 23:48
@adamraine adamraine requested review from connorjclark and removed request for a team December 13, 2022 23:48
/** 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;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should inclusion in this type imply it should be available via the cli?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We never added skipAboutBlank because it isn't useful (cli starts on about:blank anyway).

For similar reasons usePassiveGathering isn't useful on the cli because it will always test a standalone navigation and then close the page. Preserving the page state isn't useful in this scenario.

That being said, it wouldn't be difficult to include just for consistency with other options on this type.

@adamraine adamraine merged commit 437eb4d into main Jan 5, 2023
@adamraine adamraine deleted the use-passive-gathering branch January 5, 2023 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants