MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Support Lighthouse CLI

Open
#2,574 1 comment 0 reactions 2 assignees View on GitHub

@Lakshmisha-KS is already working on this.

Since Feb 12, 2025.

feature request priority-low tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
I want to run Lighthouse CLI with a WebView2 app. When the remote debugging is enabled with --remote-debugging-port, Lighthouse can successfully run but the result is not good enough:

  1. Lighthouse creates a new WebView2 Window to gather all the runner results but there is no way to intercept this Window to AddHostObjectToScript.
  2. With a little effort I make Lighthouse runs with the existing WebView2 Window, but Lighthouse cannot drive it to navigate the target, reporting a NO_FCP error.
  3. Occasionally, Lighthouse CLI reports You probably have multiple tabs open to the same origin. even with a single WebView2 Window

Describe the solution you'd like and alternatives you've considered

  • Provide an event handler when a new Window is created via DevTool protocol
  • Fix problems 2 and 3

AB#40379026

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.