W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10320] Allow an arbitrary string as the voice for forwards compatilbity

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Sep 2010 22:53:24 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OuCTE-00035k-QZ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10320


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch
             Blocks|                            |10306




--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-09-10 22:53:24 ---
This would mean that if we introduced a new element, it would end up being
considered the voice in older UAs... I guess that's not too bad...

Might be better just to go straight to have a generic voice syntax though.
<$voice> maybe? With some predefined ones? (Predefined as in having default
styles, like $narrator could be italics?) I don't know what a good syntax would
be though. <:voice> is bad because it clashes with pseudo-class syntax in CSS,
which might box us in later. *voice, !voice and +voice clash with other parts
of CSS syntax. [voice] wouldn't be hidden in older SRT UAs. Any other
suggestions? Maybe a V:voice setting on the timings line?

-- 
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 Friday, 10 September 2010 22:53:26 UTC

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