Re: [dom] DOMTokenList#toggle: don't treat everything non-undefined as true (#64)

Edge is basically reverse-engineering whatever Chrome does, bugs and all.  Can't say I blame them...

That said, the fact that Chrome mishandles the way `undefined` works when passed for an optional argument is a longstanding problem in Chrome's bindings.  We changed it to the current setup in IDL years ago to support the forwarding/proxying use cases... and then Chrome just didn't bother to implement that change.  Doing that in Chrome's bindings would help more than anything else here.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/64#issuecomment-135851754