Closed Bug 1048054 Opened 10 years ago Closed 10 years ago

Figure out a sane way to present Symbols in devtools

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1024054

People

(Reporter: bzbarsky, Unassigned)

Details

Right now, devtools have no sane way to present Symbols.  Trying to examine them directly throws "TypeError: can't convert symbol to string"; trying to console.log them fails miserably, etc.

I've been thinking a bit about what one would want to see when examining a Symbol, and it seems to me that there are two cases:

1)  This is a well-known Symbol.  In that case, saying @@iterator or Symbol.iterator or "the well-known @@iterator symbol" or something else is reasonable.

2)  This is a page-constructed Symbol.  In that case we want something like "Symbol constructed at file:line" or some such...  Do we expect |new Symbol| to be rare enough that it's OK for it to capture a stack?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.