(Sorry for the delayed reply, I apparently opted out of getting e-mails to threads I start. Weird)
Great, thank you! I updated the article a bit with the compatibility data (for Opera as well) and removed the false Symbol.prototype.name bit. ☆*PhistucK* On Tuesday, August 12, 2014 11:30:37 PM UTC+3, Erik Arvidsson wrote: > > > > > On Tue, Aug 12, 2014 at 4:03 PM, PhistucK <phis...@gmail.com> wrote: > >> Can you share a bit more about the Symbol support in Chrome 38 onwards? >> I want to expand the compatibility data in MDN >> <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol> >> a >> bit with the latest information. >> >> I understand that "Symbols" are supported. Symbol.iterator is supported >> and now Symbol.unscopables is also supported. >> What else? >> > > Those two are the only traps using symbols that have been implemented. > > >> Do Symbol.for and Symbol.keyFor do everything they should? >> > > Yes. These should work as expected. These are useful to synchronize > Symbols across globals and we use these to ensure that an iterator from one > frame is iterable in another frame. > > >> It also says Symbol.prototype.name <http://symbol.prototype.name/> exists >> only in V8 - was it removed? >> > > It has been removed from the spec and from V8. You can still get the > description by doing an explicit call to toString(). Implicit calls like + > '' and String(sym) both fails. > > -- > erik > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
