I am okay with it, as it has been confusing for me as well.
However, when faced with a decision which tag to assign to video capture issues, I usually ended up choosing Internals>Media>Capture over Blink>GetUserMedia, because I felt that the video capture code that I am touching has nothing to do with Blink directly (other than that Blink happens to expose GetUserMedia, whose implementation requires the internal video capture code).

That may be enough reason to file video capture under this tag, but Blink would not naturally be the first place for me to look for it.

Add Dale. change status to available.

I've actually argued (many times in the past) for the opposite: That we get stop using Blink>GetUserMedia and Blink>GetUserMedia>Tab, and instead use the Internals>... ones. The main reason: For tab capture, there is no web platform access to it, only an extension API, and so it makes no sense for it to be in the "Blink" bucket.

Going to move tab capture bugs out of Internals>Media>Capture and place them in a new Internals>Media>ScreenCapture component.