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="300"> |
michael@0 | 6 | <body style="overflow:hidden; height:3000px; |
michael@0 | 7 | background-image:url(repeatable-diagonal-gradient.png), url(repeatable-diagonal-gradient.png); |
michael@0 | 8 | background-attachment:fixed, scroll; |
michael@0 | 9 | background-repeat:no-repeat; |
michael@0 | 10 | background-position:0 300px;"> |
michael@0 | 11 | <!-- Test that scrolling content above background-attachment:fixed content but not |
michael@0 | 12 | intersecting it doesn't get moved down to a layer below the |
michael@0 | 13 | background-attachment:fixed content --> |
michael@0 | 14 | <div style="position:absolute; background:black; left:0; top:600px; width:500px; height:200px;"></div> |
michael@0 | 15 | </body> |
michael@0 | 16 | </html> |