This is for variables declared in the currently executing function, so it's probably not a situation where it's been optimized out.
Probably Parser.jsm choking or not handling some new exotic js. In this case, the errors should be enough to troubleshoot the problem, so anything in the browser console?
Alternatively, simply a pastebin of the sourcecode may be enough to figure this out.
FWIW, hover in a ES6 class method does not display the variable's value. You have to go over to the side and click through the stack frame to get at the value. Maybe that's what's happening here?
I'm closing this issue as the new frontend has a different implementation for preview, with issues that can be tracked here: https://github.com/devtools-html/debugger.html/issues?utf8=%E2%9C%93&q=is%3Aissue%20%5BEditorPreview%5D%20
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.