- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Mon, 27 Jan 2014 16:45:16 -0800
- To: Jatinder Mann <jmann@microsoft.com>, Arvind Jain <arvind@google.com>
- CC: Ojan Vafai <ojan@chromium.org>, Jonas Sicking <jonas@sicking.cc>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On 1/27/14 4:42 PM, Jatinder Mann wrote: > Yes, a change in behavior can be described as breaking compatibility. Yes. That's the definition of "breaking compatibility"... > It’s really an example of a change in behavior that would generally be more beneficial (e.g., power savings) than hurtful (e.g., don’t expect applications are relying on that behavior). In other words, you think the compatibility impact is small. That's a fine thing to think, especially if you have data to back it up. We need such data here. -Boris
Received on Tuesday, 28 January 2014 00:45:49 UTC