Hover the same variable shows different object between Firefox and Chrome on Windows
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(firefox138 fixed)
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: sefeng211, Assigned: hbenl)
References
Details
Attachments
(1 file, 1 obsolete file)
Thank you for helping make Firefox better. If you are reporting a defect, please complete the following:
What were you doing?
- Navigate to https://unsplash.com/s/photos/renaissance
- Click on the "Visual search" button located in the search bar.
- Open the debugger, search for
readAsDataURL, and there should be only one occurrence - Set a breakpoint at this line
- Upload an image
- This breakpoint should now be hit, and then click one frame up in the Call stack. It should be in
e.prototype._trySubscribefunction. - Hover the
evariable.
What happened?
Firefox shows an object like {lastModified: ..., name: ..., type: "image/jpeg", ...} whereas Chrome shows {closed: false, destination: ..., initialTeardown: undefined...}
What should have happened?
Should be the same.
Anything else we should know?
This is only reproducible on Windows.
| Reporter | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Thanks for the report, if you can reproduce consistently, can you try logging the object in the console as well? This way we can check if the issue is with the preview popup or not.
Comment 2•1 year ago
|
||
It actually requires previewing the e variable when we are looking at the breakpoint's frame:
File { name: "about-profiling.png", lastModified: 1730915686861, webkitRelativePath: "", size: 87598, type: "image/png" }.
I can see that value when evaluating e in the console just after pausing, before moving to the upper frame in _trySubscribe (step 6).
If I move to that upper frame, via the scopes panel (step 6), without previewing e beforehand, I see the same value as chrome:
Object { initialTeardown: undefined, closed: false, _parentage: {…}, _finalizers: (1) […], isStopped: false, destination: {…}, onFinalize: undefined, shouldUnsubscribe: undefined, _next: _next(e), _error: _error(e), … }
But if I do preview it on the breakpoint's frame, it is then shown to the same buggy value when moving in _trySubscribe frame.
Note that evaluating in the console shows the right content.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
Updated•1 year ago
|
Description
•