Justin Lebar f2560a00d6 Bug 742448 - Don't return xray-waived objects in BrowserElementAPI, and don't use the parent window's content-overridable top property for implementing window.top. r=bholley ... --HG-- extra : rebase_source : 0c81c1f605aaf73f01b47077be11345ee64955e1		2012-04-04 20:32:39 -04:00
..
browserFrameHelpers.js	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
file_empty.html	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
Makefile.in	Bug 742448 - Don't return xray-waived objects in BrowserElementAPI, and don't use the parent window's content-overridable top property for implementing window.top. r=bholley	2012-04-04 20:32:39 -04:00
test_browserFrame1.html	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
test_browserFrame2.html	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
test_browserFrame3.html	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
test_browserFrame4.html	No bug: Followups to my previous two commits.	2012-03-31 07:54:12 -07:00
test_browserFrame5.html	Bug 736688 - Part 3: Make browser frame tests run faster by loading empty pages instead of example.com/example.org (which is the huge, root mochitest file). r=smaug	2012-03-28 11:36:03 -07:00
test_browserFrame6.html
test_browserFrame7.html
test_browserFrame8.html	Bug 742448 - Don't return xray-waived objects in BrowserElementAPI, and don't use the parent window's content-overridable top property for implementing window.top. r=bholley	2012-04-04 20:32:39 -04:00