Rename Smoothness > Frame Timing

[igrigorik]

A better name to prevent mischaracterization... the API does not enable "smoothness", it provides an interface to inspect and analyze frame timing, which can be used to detect and resolve smoothness problems.

[eliperelman]

I've found that among many different companies and vendors, a pretty standard term is "Frame Uniformity".

[igrigorik]

@eliperelman that's the first time I've come across "uniformity". Aside from language, I think it suffers from same problem as smoothness -- I think it may mischaracterize what the API provides.. we don't make anything smoother or more uniform, we expose latency data about underlying frame operations.

/cc @paullewis

[eliperelman]

@igrigorik I think that's reasonable. A Frame Timing API would be the interface for insight into Frame Uniformity. +1

[paullewis]

+1. Anything that implies a desired outcome (smoothness, uniformity, consistency, reliability) should ideally be avoided.

[tobint]

+1 This seems consistent with Resource Timing and Navigation Timing APIs.