The problem affects promises (bug 1033153) 1. Open the console 2. Enter new Promise(f => f([1,2,3])) 3. Click the returned Promise object to inspect it. 4. Expand the <value> internal property. Works as expected. 5. Back in the console, enter []. 6. Click the returned Array object to inspect it. 7. Click the Promise object again. 8. Attempt to expand the <value> internal property. It won't work. And the same for proxies, because I used analogous code (bug 1274657) 1. Open the console 2. Enter new Proxy([1,2,3], {}) 3. Click the returned Proxy object to inspect it. 4. Expand the <target> internal property. Works as expected. 5. Back in the console, enter []. 6. Click the returned Array object to inspect it. 7. Click the Proxy object again. 8. Attempt to expand the <target> internal property. It won't work.

What does "it won't work" mean? Are there errors in the browser console? Crashes? Something else? Oriol, the needinfo flag is usually used when you have a question that you'd like answered by the person being flagged. Do you have a specific question of me?

(In reply to Nick Fitzgerald [:fitzgen] [⏰PDT; UTC-7] from comment #1) > Oriol, the needinfo flag is usually used when you have a question that you'd > like answered by the person being flagged. Do you have a specific question > of me? The needinfo was meant to ask whether the code you used to make promises inspectable has some problem, or if the problem is in the functions used by your code. For proxies I basically copied what you did, but I don't have much idea what's going on there. > What does "it won't work" mean? Are there errors in the browser console? > Crashes? Something else? By "it won't work" I mean the object is not expanded. See the attachment. No errors in the browser console.

Strange. I don't really remember the ins and outs of this code, I'll take a closer look after dealing with some talos regressions that are a little more urgent. ni myself to comeback to this

No time to dig in right now.

We're not using that object inspector anymore, and this bug can be closed.