- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Dec 2010 03:42:36 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11395
Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |silviapfeiffer1@gmail.com
--- Comment #4 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-12-02 03:42:34 UTC ---
My understanding of DAC-2 was that we are going to provide a menu that displays
all available tracks to the user to let the enable/disable the track display.
On top of this, there will be user settings in browsers for the preferred
tracks to be active by default. If the kind/lang combination of a track matches
a user's preferences, the track will automatically be turned on.
As for the "repetitive stimuation" issue - I guess what you are saying is that
a video that e.g. provides strobelight, and can cause seizures, should be
marked as such and not play for people who may have indicated such an
anit-preference in their browser. Are there any other such use cases where
videos are dangerous to certain user groups and must not be shown to them at
all (apart from porn, I guess)? I don't really think media queries are the
right solution for that (since it's not a property of the display media that we
are filtering on, but a user preference). I think it might be better to
introduce another attribute for such things, something like @indication which
can indicate what audience to avoid (e.g. adult, strobe etc).
Haven't made up my mind on this though, just thinking out loud...
--
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 Thursday, 2 December 2010 03:42:37 UTC