Comment 3 for bug 1791839

I think an acceptable fix would be to just add an assertion and return if no mouse capture callback is set. That's really what should have been done in the first place as it should not occur and is merely a warning for developers. User should never see this in release builds. I will make it so if there are no objections.