GoogleChrome / GoogleChrome/lighthouse

Lighthouse doesn't support frameset or measure frames

Open
#11,311 2 comments 0 reactions 0 assignees View on GitHub
feature P3
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

#### Provide the steps to reproduce
1. Run LH on

```
lighthouse http://www.franciszkanie.rybnik.pl --max-wait-for-load 70000
# or
lighthouse http://www.bl-karolina.katowice.opoka.org.pl/index.html --max-wait-for-load 70000
# or
lighthouse http://www.nspjbrzeziny.pl --max-wait-for-load 70000
```
#### What is the current behavior?
Returns an error:

`Runtime error encountered: Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_FCP)`

#### Environment Information
* Affected Channels: CLI, DevTools
* Lighthouse version: 6.2.0
* Chrome version: 84.0.4147.105
* Node.js version: v14.8.0
* Operating System: Ubuntu 20.04.1

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with one of the listed Lighthouse CLI commands and compare the CLI and DevTools behavior. Done means Lighthouse can process pages using frameset or frames without the NO_FCP trace error; the issue names no files or tests, so locating the relevant handling will require project research.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, frontend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.