Open Bug 1446283 Opened 7 years ago Updated 2 years ago

Empty rule-view with browser console errors

Categories

(DevTools :: Inspector: Rules, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: pbro, Unassigned)

References

Details

Somewhat complicated steps, but this results in an empty rule-view, so kind of bad: - first open the console in a tab - then open the browser toolbox - from the inspector in the browser toolbox, inspect some elements in the "content" console panel - now, in the "content" toolbox, switch to the inspector --> the rule-view is empty, and some errors appear in the browser console: "content.text is undefined". Unfortunately the error is being thrown by a generic catch-all error in the rule-view, and I couldn't get the stack trace (and now, trying to reproduce again, I couldn't). But searching for this string in the code, it looks like it's netmonitor related: devtools/server/actors/stylesheets.js: fetchStylesheetFromNetworkMonitor.
Priority: -- → P2
Hmm, a bit hard to know the best approach if we can't reproduce... But, we could potentially add `|| !content.text` here, since the lines following assume it is set: https://searchfox.org/mozilla-central/rev/3abf6fa7e2a6d9a7bfb88796141b0f012e68c2db/devtools/server/actors/stylesheets.js#475
Product: Firefox → DevTools
See Also: → 1636660
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.