- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Aug 2016 15:33:13 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 --- Comment #78 from Travis Leithead [MSFT] <travil@microsoft.com> --- I'm sympathetic to the memory problem, but we have to balance web compat against any mitigation we take to alleviate leaks. For instance, Edge is currently very aggressive at countering leaks (in iframe navigation scenarios only), but we pay a cost for a large number of broken websites that expect to keep access to certain "leaked" data. You could argue that our leak-breaking logic (which is very old and not originally intended to fix these described leaks anyway) is not the best/right approach, and would agree with you, but it has at least given us some insight in the potential side-effects. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 22 August 2016 15:33:23 UTC