If you use display capture, you should have no problem capturing and the ability to turn off the cursor with Capture Cursor disabled.
If you use game capture, chrome is blacklisted from using this capture method.
If you use window capture, the Capture Cursor property sometimes appears, sometimes doesn't. For Chrome and Edge, the property never added to the dialog item list (maybe a bug or by design). Both Chrome and Edge use tabs which are child windows attached to a parent window. In such a UI arrangement, it would be a pain in the ass to have to support every Windows application on a case by case basis if the "Viewable content" that people record/stream is setup like this. Windows capture works fine for programs with a single parent window. Programs like Notepad, Task Manager, and such. Thats where its best used.
But for applications like Chrome and Edge, OBS has to do per application window detection and know exactly what it is looking for. Its best to use display capture.
