Intent to Remove: Prefixed Resource Timing buffer-management API

瀏覽次數:57 次
跳到第一則未讀訊息

Kunihiko Sakamoto

未讀,
2017年1月5日 下午11:42:082017/1/5
收件者:blink-dev

Primary eng (and PM) emails

ksak...@chromium.org


Link to “Intent to Deprecate” thread

No deprecate thread; a deprecation message was added as part of the Intent to ship unprefixed Resource Timing API.


Summary

Remove webkitClearResourceTimings(), webkitSetResourceTimingBufferSize(), and onwebkitresourcetimingbufferfull from the Performance interface, in favor of clearResourceTimings(), setResourceTimingBufferSize(), and onresourcetimingbufferfull.


Motivation

This aligns ResourceTiming with the specification and Chrome’s general desire of not using prefixed features anymore.


Compatibility Risk

Low.

The webkit-prefixed APIs have been supported since Chrome 25 (Feb 2013). It was originally implemented in WebKit, but Safari has not enabled it. Firefox, IE 10+, and Edge have only unprefixed version of the API.

Deprecation message has been around for a long time, since Chrome 46 (Oct 2015).


Usage information from UseCounter

PrefixedPerformanceClearResourceTimings: 0.006%

PrefixedPerformanceSetResourceTimingBufferSize: 0.001%

PrefixedPerformanceResourceTimingBufferFull: 0.025%


The usage of onresourcetimingbufferfull is probably inflated since it's measuring any access to the attribute (not when events are actually fired).


OWP launch tracking bug

https://crbug.com/678547


Entry on the feature dashboard

https://www.chromestatus.com/feature/5688905986736128

Ilya Grigorik

未讀,
2017年1月6日 上午12:20:442017/1/6
收件者:Kunihiko Sakamoto、blink-dev
\o/ .. yay! 

Dimitri Glazkov

未讀,
2017年1月6日 上午12:35:402017/1/6
收件者:Ilya Grigorik、Kunihiko Sakamoto、blink-dev
LGTM1

Chris Harrelson

未讀,
2017年1月6日 上午11:37:542017/1/6
收件者:Dimitri Glazkov、Ilya Grigorik、Kunihiko Sakamoto、blink-dev
LGTM2

LGTM1
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

PhistucK

未讀,
2017年1月6日 下午12:37:572017/1/6
收件者:Chris Harrelson、Dimitri Glazkov、Ilya Grigorik、Kunihiko Sakamoto、blink-dev
I thought there was an "Alternatives for web developers" section in the intent template, or is it only in the intent to deprecate template?

I know the summary already states it, but it is better to spell it out in its own section (and on ChromeStatus) for easier look up for web developers.


PhistucK

Kunihiko Sakamoto

未讀,
2017年1月9日 下午10:36:172017/1/9
收件者:PhistucK、Chris Harrelson、Dimitri Glazkov、Ilya Grigorik、Kunihiko Sakamoto、blink-dev
Yeah the alternatives section was only in the intent-to-deprecate template.

For this case, alternatives are the unprefixed buffer-management API:
  • performance.clearResourceTimings()
  • performance.setResourceTimingBufferSize()
  • performance.onresourcetimingbufferfull

Rick Byers

未讀,
2017年1月10日 下午2:21:282017/1/10
收件者:Kunihiko Sakamoto、PhistucK、Chris Harrelson、Dimitri Glazkov、Ilya Grigorik、blink-dev
LGTM3
回覆所有人
回覆作者
轉寄
0 則新訊息