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 | <!DOCTYPE HTML> |
michael@0 | 2 | <html reftest-async-scroll |
michael@0 | 3 | reftest-displayport-x="0" reftest-displayport-y="0" |
michael@0 | 4 | reftest-displayport-w="800" reftest-displayport-h="2000" |
michael@0 | 5 | reftest-async-scroll-x="0" reftest-async-scroll-y="50"> |
michael@0 | 6 | <body style="overflow:hidden; height:3000px"> |
michael@0 | 7 | <!-- test that a fixed-pos element whose contents are interleaved in z-order |
michael@0 | 8 | with non-scrolling content works correctly with async scrolling --> |
michael@0 | 9 | <div style="position:absolute; top:25px; left:0; width:100px; height:200px; background:yellow; z-index:1"></div> |
michael@0 | 10 | <div style="position:fixed; background:blue; top:0; left:0; width:200px; height:100px"> |
michael@0 | 11 | <div style="position:absolute; background:cyan; top:40px; left:0; width:50px; height:300px;"></div> |
michael@0 | 12 | </div> |
michael@0 | 13 | </body> |
michael@0 | 14 | </html> |