Again, I'd prefer to see this scenario integrated into capture.html - no real need to force the user to do a manual step just for this little error-case.  Plus then we'll verify that setPointerCapture/releasePointerCapture on invalid pointer IDs doesn't somehow break subsequent setPointerCapture/releasePointerCapture calls on legitimate pointer IDs