Need to define limitations of JS client compatibility with DASH264

[BuildManager]

For example, HE-AACv2.

[wilaw]

Please provide more info for this bug. HE-AACv2 is supported by Chrome, so not sure how that is an example of a limitation. Are you looking for a list of DASH-AVC/264 tests vectors and whether they are compliant or not with the existing versions of Chrome? Should this be a constantly updated list (since Chrome is evolving weekly with respect to MSE and EME) or a snapshot in time? Should we separate what is technically possible to decode in Chrome but not yet ready in the player, from what Chrome cannot support and therefore the client cannot render?

[BuildManager]

First, I used HE-AACv2 as an example under the misunderstanding that it was NOT supported.

Two broader question are still appropriate, Is the JS client targeted for qualification against DASH264? and What does that mean?

I suggest that this Issue be closed due to lack of specifics related to the JS Client and that more specific DASH264 related Issues be added as needed.