- From: Liang,Tao <liangtao01@baidu.com>
- Date: Wed, 22 Oct 2014 08:58:09 +0000
- To: "Aaron Heady (BING AVAILABILITY)" <aheady@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
I agree with Aaron Heady's advice. In fact, it's useful to see the release's effect on crash for global user base and to supply a way to improve the product. But does Navigation have an opportunity to logging Crash / Breeze ? -----邮件原件----- 发件人: Aaron Heady (BING AVAILABILITY) [mailto:aheady@microsoft.com] 发送时间: 2014年10月22日 4:25 收件人: public-web-perf@w3.org 主题: RE: W3C Navigation Error Logging - log when UA crash/freeze? Any thoughts on this? -----Original Message----- From: Aaron Heady (BING AVAILABILITY) Sent: Tuesday, October 14, 2014 1:38 PM To: 'public-web-perf@w3.org' Subject: W3C Navigation Error Logging - log when UA crash/freeze? Curious about a possible addition to the scope of what logging covers. Does anything in the spec capture when a page load crashes the browser tab or causes it to be unresponsive? We ran into an obscure situation that we hadn’t tested for and managed to get a UA to crash, looks like it was related to a style recalculation. Could we/should we log an error entry on the page/domain when the UA crashes/freezes, so we can see at scale that something we released is increased the crash/freeze rate for the global user base? Thoughts? Aaron
Received on Wednesday, 22 October 2014 08:58:46 UTC