Intent to Implement and Ship: <time> element

120 views
Skip to first unread message

TAMURA, Kent

unread,
Jun 28, 2017, 8:27:29 PM6/28/17
to blink-dev

Contact emails

tk...@chromium.org



Spec

https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-time-element



Summary

<time> element. It's a simple HTMLElement with a single reflected attribute.


The same intent was sent in 2013, and it was rejected.

https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/gRBe04ji0Rk/xgx4ljz8yCMJ

However, three other major browsers implemented it, and we should implement it for interoperability.


Though we haven't implemented the feature yet, we already have a UseCounter.

https://www.chromestatus.com/metrics/feature/timeline/popularity/1100

1.0% to 1.2% of page views use <time> element.



Motivation

- Improve interoperability. Edge, Firefox, and Safari shipped it.



Interoperability and Compatibility Risk

Very low. Small additional feature.


Edge: Shipped

Firefox: Shipped

Safari: Shipped

Web developers: Positive. A feature request bug was filed by a user.



Ongoing technical constraints

None.



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.



Is this feature fully tested by web-platform-tests?

Yes.

/html/dom/interfaces.html

/html/dom/reflection-text.html

/html/semantics/text-level-semantics/the-time-element/001.html



OWP launch tracking bug

crbug.com/655921



Link to entry on the feature dashboard

https://www.chromestatus.com/features/5633937149788160



Requesting approval to ship?

Yes.




--
TAMURA Kent
Software Engineer, Google


Daniel Bratell

unread,
Jun 29, 2017, 9:50:23 AM6/29/17
to blink-dev, TAMURA, Kent
On Thu, 29 Jun 2017 02:26:59 +0200, TAMURA, Kent <tk...@chromium.org> wrote:

Though we haven't implemented the feature yet, we already have a UseCounter.

https://www.chromestatus.com/metrics/feature/timeline/popularity/1100

1.0% to 1.2% of page views use <time> element.


Surprisingly high number. Do you have any examples how it is used?

I don't mind this being implemented, just curious.

/Daniel


--
/* Opera Software, Linköping, Sweden: CET (UTC+1) */

TAMURA, Kent

unread,
Jun 30, 2017, 3:50:34 AM6/30/17
to Daniel Bratell, blink-dev
I checked some sites found by HTTP Archive.
 - Many many sites use <time>, rather than a few extremely popular sites
 - A popular usage is to mark up timestamps of items in "What's new" section.
 - itemprop= is frequently used together.  I guess CMSs generate <time>.


--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.y2lkpxt4rbppqq%40cicero2.linkoping.osa.

Philip Jägenstedt

unread,
Jun 30, 2017, 5:01:44 AM6/30/17
to TAMURA, Kent, Daniel Bratell, blink-dev
LGTM1

I was the sender of the failed intent in 2013, and I actually agree that this isn't a very meaningful thing to implement/ship, but that ship has sailed with 3 other engines already doing it.

Mike West

unread,
Jun 30, 2017, 8:35:27 AM6/30/17
to Philip Jägenstedt, TAMURA, Kent, Daniel Bratell, blink-dev
LGTM2. I'm pretty sure I use `<time>` on the blog I haven't updated in 4 years, so it'll give me a nice warm feeling in the cockles of my heart to know that it's no longer represented as `HTTPUnknownElement`.

-mike

Chris Harrelson

unread,
Jun 30, 2017, 3:46:15 PM6/30/17
to Mike West, Philip Jägenstedt, TAMURA, Kent, Daniel Bratell, blink-dev
LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3Df4SxZK06PF6%2BoE_tX9aKbhjVgx4M13gzrJG4J2ZgJFtg%40mail.gmail.com.

Reply all
Reply to author
Forward
0 new messages