New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 593904 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Ensure media track language is always BCP47 language code

Project Member Reported by servolk@chromium.org, Mar 10 2016

Issue description

Currently there seems to be a mismatch between https://dev.w3.org/html5/html-sourcing-inband-tracks/#mpeg4 (which recommends that the language property of the media tracks should be the 'Content of the language field in the MediaHeaderBox' which is 3-letter ISO 639-2 language id) and HTML5 spec https://html.spec.whatwg.org/multipage/embedded-content.html#dom-audiotrack-language (which specifies that A/V track language should be a BCP47 language tag, which looks like e.g. "en-US"). The BCP47 language tag might be present in ELNG box in some .mp4 files (although it's not very common yet). We need to sort it out and ensure that user-visible JS-level properties always return either proper BCP47 language tags or empty strings.
See also discussion at https://codereview.chromium.org/1735003004/ for more details.
 
Cc: phil...@opera.com
Components: Internals>Media>Source
Labels: MSEscrubbed
+MSE label, since MSE spec refers to similar BCP47 requirement as part of extending HTMLMediaElement's track-related attributes.
Note that that inband track attribute sourcing spec is a draft. It asks for feedback to be sent to public-inbandtracks at w3.org.
Cc: -phil...@opera.com
Owner: phil...@opera.com
Status: Assigned (was: Untriaged)

Comment 5 by phil...@opera.com, Mar 29 2016

Cc: -servolk@chromium.org phil...@opera.com
Owner: servolk@chromium.org

Comment 6 by foolip@chromium.org, Nov 11 2016

Cc: foolip@chromium.org

Comment 7 by foolip@chromium.org, Nov 11 2016

Cc: -phil...@opera.com

Sign in to add a comment