Comment 1 for bug 2052567

The good news is that bug 1993823 is coming along so you're right about that being the real fix. The point about DOM.whatevs is a good one, I wonder if that was leftover from the XUL days or something, ick.

This bug probably shouldn't be marked invalid or won't fix or anything like until the Angular reporter is available that so that people can find this bug in case they run into it; thanks for tracking this down James!