- From: Jatinder Mann <jmann@microsoft.com>
- Date: Tue, 28 Jan 2014 00:42:28 +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>
Yes, a change in behavior can be described as 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). Since it’s still a hard problem to solve, I’m not advocating that we fix that example, I only used it as an illustration. -----Original Message----- From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] Sent: Monday, January 27, 2014 3:38 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 2:39 PM, Jatinder Mann wrote: > An example of a good change in Page Visibility that won't break compatibility is if we fix the obscured browser window case to correctly return hidden instead of visible. Why do you think it doesn't break compatibility? It clearly does. The question is whether anyone is relying on the current behavior... -Boris
Received on Tuesday, 28 January 2014 00:42:58 UTC