The "SourceBuffer monitoring" algorithm in Section 2.4.4 and the "Coded frame processing" algorithm in Section 3.5.8 don't use the same criteria for transitioning the HTMLMediaElement.readyState to HAVE_FUTURE_DATA.

SourceBuffer monitoring text:
"If buffered for at least one object in activeSourceBuffers contains a TimeRange that includes the current playback position but not enough data to ensure uninterrupted playback:"

Coded frame processing algorithm text:
"If the HTMLMediaElement.readyState attribute is HAVE_CURRENT_DATA and the new coded frames cause all objects in activeSourceBuffers to have media data beyond the current playback position, then run the following steps:"


I propose that the SourceBuffer monitoring text be updated to the following:
"If buffered for all objects in activeSourceBuffers contains a TimeRange that includes the current playback position and some time beyond the current playback position, but not enough data to ensure uninterrupted playback:"

I believe this will bring the 2 algorithms into sync and avoid potential readyState oscillations caused by different criteria being used.