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.

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

Add ability to specify min/start time for custom waterfalls #3042

Open
jspurlin opened this issue Feb 9, 2024 · 2 comments
Open

Add ability to specify min/start time for custom waterfalls #3042

jspurlin opened this issue Feb 9, 2024 · 2 comments
Labels
Type: Enhancement An improvement to WebPageTest

Comments

@jspurlin
Copy link

jspurlin commented Feb 9, 2024

Feature Request Summary

This is a request to add the ability to set a min/start time for custom waterfalls. Today you can specify a max/end time, but no start time.

What's the motivation or use case for the change/feature?

I want the ability to "zoom in" on a specific chunk of time from the waterfall, say 2-3.5s for example. Today I can only see 0-3.5s

@jspurlin jspurlin added the Type: Enhancement An improvement to WebPageTest label Feb 9, 2024
@slightlyoff
Copy link

This is a request coming from MSFT's use of WPT internally. I don't have edit permissions on the bug, but if the owners here feel like it would be best for us to contribute patches in support of this, let us know.

/cc @pmeenan @andydavies

@jspurlin jspurlin changed the title Add ability to specify min/start time to custom waterfalls Add ability to specify min/start time for custom waterfalls Feb 9, 2024
@pmeenan
Copy link
Contributor

pmeenan commented Feb 12, 2024

FWIW, I'm happy to review PR's or answer any questions (or finally take a crack at it myself) but I don't have repository permissions to merge so that part would depend on Catchpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement An improvement to WebPageTest
Projects
None yet
Development

No branches or pull requests

3 participants