- From: <bugzilla@jessica.w3.org>
- Date: Mon, 31 Oct 2011 17:48:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240
Patrick Arlt <patrick.arlt@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick.arlt@gmail.com
--- Comment #52 from Patrick Arlt <patrick.arlt@gmail.com> 2011-10-31 17:48:18 UTC ---
So we create a <time> element that is used to markup times in a document,
decide that it is to specific and replace is with a <data>element that can only
be used to mark up time? this doesn't make much sense. Its much less semantic
and will lead to confusion with the data-* attribute.
There is also a fourth use case where you could easily access all <time>
elements from javascript to transform them e.g. to human relative time while
keeping a machine readable time in the datetime attribute.
Why not just add a generic data attribute. Why take away something that is
actively being used?
--
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 Monday, 31 October 2011 17:48:26 UTC