The frames() timing function should now be in the next release of Chrome (60).
The next step on this issue is to send an intent to deprecate and remove for step-middle, targeting 61 for deprecation and 62 for removal. So, next action will be in a month or so.
Requesting to merge ffcd346677e9dd28037da9619c510274d9318bfe into M60 beta.
This is to prevent us shipping a web feature that may become spec incompatible in the near future.
The bug is marked as P3 or Feature. It should not be merged as M60 is in beta.
Please contact the approriate milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Ping: abdulsyed
We are attempting to co-ordinate with Firefox to avoid shipping a web feature that's under spec contention. Please manually review the request to merge https://crrev.com/ffcd346677e9dd28037da9619c510274d9318bfe into M60.
This bug requires manual review: We are only 11 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by suzyh@chromium.org
, Oct 5 2016