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

[REGRESSION]: Snapshot styles in trace-viwer aren't loaded #24144

Closed
fadezak100 opened this issue Jul 10, 2023 · 5 comments · Fixed by #24145
Closed

[REGRESSION]: Snapshot styles in trace-viwer aren't loaded #24144

fadezak100 opened this issue Jul 10, 2023 · 5 comments · Fixed by #24145
Labels

Comments

@fadezak100
Copy link

Context:

  • GOOD Playwright Version: 1.35.0
  • BAD Playwright Version: 1.36.0-next
  • Operating System: Tested on both Windows and MacOs

Code Snippet
I was running a local version of trace-viewer. I had earlier generated some trace.zip reports from a playwright test. After loading the tests on the trace-viewer, I noticed that in most of the reports, snapshot styles were missing.

Describe the bug

When loading a trace.zip into the local trace-viewer package some of the snapshot styles resources aren't loaded. When inspecting the network requests I found out that all of the CSS files were returned but some of them were empty.

missedupstyles

The live trace viewer which is still on 1.35.0 I believe:
Screen Shot 2023-07-11 at 2 17 02 AM

@dgozman
Copy link
Contributor

dgozman commented Jul 10, 2023

@fadezak100 Any chance for a repro we can run locally, or a trace.zip that exhibits this issue?

@fadezak100
Copy link
Author

@dgozman Sure the one I have right now has a LinkedIn account credentials I will try to generate one for you. Or if I can send the one I already have privately?

@dgozman
Copy link
Contributor

dgozman commented Jul 10, 2023

@fadezak100 You can send it to dgozman [at] microsoft [dot] com

@fadezak100
Copy link
Author

@dgozman sent.

dgozman added a commit that referenced this issue Jul 11, 2023
Fixes #24144.

Previously, we only matched by url, which confuses GET and HEAD requests
where the latter is usually zero-sized.

Also make sure that resources are sorted by their monotonicTime, since
that's not always the case in the trace file, where they are sorted by
the "response body retrieved" time.
dgozman added a commit to dgozman/playwright that referenced this issue Jul 11, 2023
Fixes microsoft#24144.

Previously, we only matched by url, which confuses GET and HEAD requests
where the latter is usually zero-sized.

Also make sure that resources are sorted by their monotonicTime, since
that's not always the case in the trace file, where they are sorted by
the "response body retrieved" time.
aslushnikov pushed a commit that referenced this issue Jul 11, 2023
Fixes #24144.

Previously, we only matched by url, which confuses GET and HEAD requests
where the latter is usually zero-sized.

Also make sure that resources are sorted by their monotonicTime, since
that's not always the case in the trace file, where they are sorted by
the "response body retrieved" time.
@dgozman
Copy link
Contributor

dgozman commented Jul 11, 2023

@fadezak100 Could you please try @playwright/test@next and check that trace works for you now?

@dgozman dgozman added the v1.37 label Aug 2, 2023
Germandrummer92 pushed a commit to OctoMind-dev/playwright that referenced this issue Oct 27, 2023
Fixes microsoft#24144.

Previously, we only matched by url, which confuses GET and HEAD requests
where the latter is usually zero-sized.

Also make sure that resources are sorted by their monotonicTime, since
that's not always the case in the trace file, where they are sorted by
the "response body retrieved" time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants