Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Phone #14835

Closed
ftservice opened this issue Feb 28, 2023 · 0 comments · Fixed by #14828, #14827, #14819, #14823 or #14826
Closed

Phone #14835

ftservice opened this issue Feb 28, 2023 · 0 comments · Fixed by #14828, #14827, #14819, #14823 or #14826
Assignees
@brendankenny
Labels
needs-priority

Comments

@ftservice
Copy link

Feature request summary

What is the motivation or use case for changing this?

How is this beneficial to Lighthouse?
This was linked to pull requests Feb 28, 2023
core(legacy-javascript): update polyfill size graph #14828
Merged
core(legacy-javascript): add focus-visible polyfill #14827
Merged
Create photo.py #14825
Closed
core: don't use failed network requests as potential initiators #14819
Merged
core(bf-cache): count failures based on affected frames #14823
Merged
misc(proto): bump next id #14826
Merged
core: add initiatorRequest from async stacks and preloads #14741
Merged
core: refactor out entity-classification lookup tables #14744
Merged
report: avoid really slow regexes for long urls #14745
Merged
core(tracing): handle FrameCommittedInBrowser with processPseudoId #14800
Merged
@adamraine adamraine closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2023
@GoogleChrome GoogleChrome locked as spam and limited conversation to collaborators Feb 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@brendankenny brendankenny

Labels
needs-priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

core(legacy-javascript): update polyfill size graph GoogleChrome/lighthouse
core(legacy-javascript): add focus-visible polyfill GoogleChrome/lighthouse
core: don't use failed network requests as potential initiators GoogleChrome/lighthouse
core(bf-cache): count failures based on affected frames GoogleChrome/lighthouse
misc(proto): bump next id GoogleChrome/lighthouse
core: add initiatorRequest from async stacks and preloads GoogleChrome/lighthouse
core: refactor out entity-classification lookup tables GoogleChrome/lighthouse
report: avoid really slow regexes for long urls GoogleChrome/lighthouse
core(tracing): handle FrameCommittedInBrowser with processPseudoId GoogleChrome/lighthouse
Create photo.py Monika437/lighthouse
4 participants
@brendankenny @ftservice @adamraine @devtools-bot