- From: Jatinder Mann <jmann@microsoft.com>
- Date: Tue, 28 Jan 2014 00:57:39 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>, 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>
Again, I don't think we should make that particular change, so it's probably not necessary to get that data. I do think we should focus on trying to solve Element Visibility. I'll make sure we include it on the agenda for this week's conference call discussion. It'd be great if you could join us! -----Original Message----- From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] Sent: Monday, January 27, 2014 4:45 PM To: Jatinder Mann; Arvind Jain Cc: Ojan Vafai; Jonas Sicking; public-web-perf@w3.org Subject: Re: making page visibility a property of document instead of top level browsing context 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:58:19 UTC