W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 12141] Specifically state that all <track> options be exposed to the end user

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Feb 2011 00:37:53 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Ps2jp-0005La-QH@jessica.w3.org>

Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |silviapfeiffer1@gmail.com

--- Comment #6 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-02-23 00:37:52 UTC ---
(In reply to comment #5)
> (In reply to comment #3)
> > I am not sure I agree completely.  The example given is a clear case, but what
> > if (hypothetically) the UA knows it is audio-only (e.g. for a non-sighted user)
> > and there are sign-language tracks? Why offer them to the end-user at all?
> > 
> > Some kind of UA discretion should still be allowed.
> How would the UA know whether a non-sighted user would want access to the
> sign-language tracks or not? I feel it is a slippery slope when we presume to
> know what any given user 'wants'. 
> If UA's wish to offer a filtering mechanism, then that is a feature of that UA
> - however the default should still be as suggested and filtering be a
> user-option. (I've long adhered to the axiom 'author proposes, user disposes'.)

I guess the comment that Dave makes is that the UA should have the possibility
to decide what tracks to expose to a user through a track menu that is
automatically displayed as part of the video controls.

I am further assuming that the idea is that if a user has set their preferences
to be to not see any video tracks (e.g. because they are blind or have their
eyes elsewhere) and therefore prefer to always activate the first appropriate
audio descriptions track (being appropriate because it's in their preferred
language) then the UA should not display these unwanted tracks in the track
selection menu.

I am further assuming that the idea is that this would remove complexity from
the user and simplify their choices - in particular where there is little real
estate as on a mobile device.

(Dave, correct me if I am falsely assuming your line of thought.)

I actually think that this should be a user preference setting, too - or
something that the browsers implement dependent on the available real estate
and user preferences. But as a default, I agree with John that all of the
available tracks should be displayed.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 23 February 2011 00:37:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:41 UTC