Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Side by Side Diff: chrome/content/harness.js

Issue 5745141503492096: Issue 1561 - Move unit tests out of the browser`s content area (Closed)
Patch Set: Addressed comment Created Nov. 17, 2014, 6:57 p.m.
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View unified diff | Download patch
« no previous file with comments | « chrome.manifest ('k') | chrome/content/harness.xul » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 // Some people actually switch off browser.frames.enabled and are surprised
2 // that things stop working...
3 window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
4 .getInterface(Components.interfaces.nsIWebNavigation)
5 .QueryInterface(Components.interfaces.nsIDocShell)
6 .allowSubframes = true;
7
8 window.addEventListener("load", startTests, false);
9
10 function startTests()
11 {
12 document.getElementById("tests").setAttribute("src", "index.html" + location.s earch);
13 }
OLDNEW
« no previous file with comments | « chrome.manifest ('k') | chrome/content/harness.xul » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld