Tue, 06 Jan 2015 21:39:09 +0100
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
michael@0 | 1 | <style> |
michael@0 | 2 | body { overflow: scroll } |
michael@0 | 3 | div { |
michael@0 | 4 | width: 10px; |
michael@0 | 5 | height: 10px; |
michael@0 | 6 | background-color: #d64203; |
michael@0 | 7 | } |
michael@0 | 8 | </style> |
michael@0 | 9 | |
michael@0 | 10 | <body> |
michael@0 | 11 | <div style="width: 50vw"></div> |
michael@0 | 12 | <div style="height: 25vh"></div> |
michael@0 | 13 | <div style="width: 35vmin"></div> |
michael@0 | 14 | <div style="height: 25vmax"></div> |
michael@0 | 15 | |
michael@0 | 16 | <!-- |
michael@0 | 17 | Ensure that the scroller positioned the same way as it would be in the |
michael@0 | 18 | 'overflow: auto' case. We'll have scrollbars either way, but we don't |
michael@0 | 19 | want the '!=' reftest to spuriously succeed because of the scrollers. |
michael@0 | 20 | --> |
michael@0 | 21 | <div style="width: 500px; height: 500px; background-color: black"> |
michael@0 | 22 | </body> |