As a part of onion soup it makes sense to switch away from having WebMediaPlayer know anything about ready states or network states. Instead it should more closely resemble a callback driven interface.

This constant worry about ready states and when it can/should be switched in response to under the hood operations in a constant source of bugs. I.e.  issue 873837  most recently. We've had issues in the past with things like play not being delivered prior to have enough data too.

Having things like the seek API be callback driven instead of implicitly signaled by a ready state change would simplify the interface significantly. Removing knowledge of ready states would simplify things around "have_future_data" and it's implications for play.

+few folks who probably care about this stuff.