Actually, after looking into it a bit more, I think I'm a fan of what chrome is doing. Here is a small test case [dbg-shadow](https://dbg-shadow.glitch.me). In general, I think it is helpful in this UI to visualize the scopes because they could be meaningful to the users. In this case, top-level const are just not helpful and should be a separate case. I think your initial patch was good in that it differentiates function lexicals and lets the UI do the merging. -- We're currently working on inline variable preview [bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1547385), [doc](https://docs.google.com/document/d/1_vCOdOmrGyHWXThds5F6ZkSfvoeIamQnwM4B8FAYZvg/edit#heading=h.8uq5fr5mdo7m), which i hope will do a better job of helping users see the most relevant values.
Bug 1448166 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Actually, after looking into it a bit more, I think I'm a fan of what chrome is doing. Here is a small test case [dbg-shadow](https://dbg-shadow.glitch.me). In general, I think it is helpful in this UI to visualize the scopes because they could be meaningful to the users. In this case, top-level const are just not helpful and should be a separate case. I think your initial patch was good in that it differentiates function lexicals and lets the UI do the merging. -- We're currently working on inline variable preview [bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1547385), [doc](https://docs.google.com/document/d/1_vCOdOmrGyHWXThds5F6ZkSfvoeIamQnwM4B8FAYZvg/edit#heading=h.8uq5fr5mdo7m), which i hope will do a better job of helping users see the most relevant values. But either way, I think the scopes pane should show most block scopes, while somewhere else we help users see the most relevant _local_ values