From 1d3156a845b709a762be32275a69fc9c14496179 Mon Sep 17 00:00:00 2001 From: Nolan Lawson Date: Thu, 17 Nov 2016 15:53:41 -0800 Subject: [PATCH] Update 2016-11-16-react-v15.4.0.md Edge and IE11 both show user marks and measures in the Dev Tools, so it's technically not accurate to say that only Chrome has this feature. --- _posts/2016-11-16-react-v15.4.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2016-11-16-react-v15.4.0.md b/_posts/2016-11-16-react-v15.4.0.md index 83f20fea..83edea5e 100644 --- a/_posts/2016-11-16-react-v15.4.0.md +++ b/_posts/2016-11-16-react-v15.4.0.md @@ -41,7 +41,7 @@ To use it: Note that the numbers are relative so components will render faster in production. Still, this should help you realize when unrelated UI gets updated by mistake, and how deep and how often your UI updates occur. -Currently Chrome is the only browser supporting this feature, but we use the standard [User Timing API](https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API) so we expect more browsers to add support for it. +Currently Chrome, Edge, and IE are the only browsers supporting this feature, but we use the standard [User Timing API](https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API) so we expect more browsers to add support for it. ### Mocking Refs for Snapshot Testing