Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] HTML report served from file:// url and trace attachments
See original GitHub issue- configure tracing as
on - generate an HTML report
- open html report as a static HTML, navigating to its
file://url - try opening trace attachment in the HTML report
Expected: trace viewer is opened, or maybe navigated to online viewer? Actual: blank screen
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
346135 - Security: html files from file URLs can read data from ...
I've been thinking of ways to fix this. One potential way is taint tracking--if a drag is marked as tainted (e.g. renderer originated),...
Read more >[BUG] Html report only allow first trace to be viewable link, and ...
EXE npm: 8.1.0 - C:\Program Files\nodejs\npm. ... [BUG] Html report only allow first trace to be viewable link, and remaining traces are ...
Read more >Cannot attach a file to a bug - Visual Studio Feedback
When trying to attach a file to a bug, Edge will just hang after I click on the "Add attachment" link. When trying...
Read more >Possibility to attach a file to an event - Bugzilla@Mozilla
Currently to associate a file with an event you must type the entire URL into the URL box. The ability to browes the...
Read more >2.3. Understanding a Bug — Bugzilla 5.0.6 documentation
A flag is a kind of status that can be set on bugs or attachments to indicate that the bugs/attachments are in a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, so I believe this will self-fix with 1.17 that is about to go live tomorrow. You can already give it a try with @1.17.0-rc1. Please let us know if it does not work for you!
The 1.19.2 have the same issue at my docker, but the 1.18.1 at my macos wrok well