The Android platform unfortunately does not support HLS w/ fMP4 segments and Apple has provided no guidance on how to differentiate TS vs fMP4 segments in canPlayType().

To ensure fallback to a potentially supported source, we should make sure that MediaPlayer preparation errors are treated in such a way as to trigger the "next source" handling in HTMLMediaElement:

https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp?l=1571
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp?l=940

We currently deliver any loading errors after providing (fake) metadata; which prevents the resource selection algorithm from running since we are no longer < kHaveMetadata. We need to either ensure these errors are delivered prior to kHaveMetadata (hard, because we don't want to load MediaPlayer until the user actually wants it) or figure out some way for these errors to directly invoke the resource selection algorithm.