Pretty-printing an anonymous file while paused in it causes debugger UI to turn white
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(firefox80 fixed)
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: Honza, Assigned: loganfsmyth)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This is cloned from https://github.com/firefox-devtools/debugger/issues/8270
STR:
- Go to http://walmart.decipherinc.com/survey/selfserve/53a/wal18003
- Go to debugger
- Activate Event Listener Breakpoints: "click"
- Tap on Continue at the bottom of the page (the debugger opens)
- click { } at the bottom of the window
AR: The Debugger panel content is blank
ER: The Debugger (pretty printing) works as expected.
This doesn't look like being related to pretty printing itself since the formatted source appears for a moment and than it breaks.
There is an error in the Browser Console
Error: Resource source-server0.conn0.child2/source42/originalSource-21eb1fc094f510399f0fb9e6f2c15d92 does not exist selector.js:37:11
The above error occurred in the <Connect(DebugLine)> component:
in Connect(DebugLine) (created by Editor)
in div (created by Editor)
in div (created by Editor)
in Editor (created by Connect(Editor))
in Connect(Editor) (created by App)
in div (created by App)
in div (created by App)
in div (created by SplitBox)
in div (created by SplitBox)
in SplitBox (created by App)
in div (created by SplitBox)
in div (created by SplitBox)
in SplitBox (created by App)
in div (created by A11yIntention)
in A11yIntention (created by App)
in div (created by App)
in App (created by Connect(App))
in Connect(App)
in Provider
in Provider
Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries. react-dom-dev.js:17252:13
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Logan, can you please look at this one.
What do you think should be the meta in this case?
Thanks!
Honza
Comment 2•5 years ago
|
||
:Honza, if you think that's a regression, then could you try to find a regression range in using for example mozregression?
Assignee | ||
Comment 3•5 years ago
|
||
We're accidentally creating mismatched sourcemapping information for the pretty-printed file so while pretty-printing succeeds, when we query the worker for position information, we get back a non-existent source ID, and when we try to use that source ID to highlight the DebugLine, it throws.
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Comment 6•5 years ago
|
||
bugherder |
Description
•