Skip to content

Commit

Permalink
Fix comments in BackgoundFrame.
Browse files Browse the repository at this point in the history
  • Loading branch information
Paul-E committed Jun 12, 2014
1 parent 37bad44 commit f5ba12e
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions src/backgroundframe-link.js
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ if (typeof fdom === 'undefined') {
fdom.link = fdom.link || {};

/**
* A port providing message transport between two freedom contexts via iBackgroundFrames.
* A port providing message transport between two freedom contexts via iFrames
* on the global backgound page.
* @class link.BackgroundFrame
* @extends Link
* @uses handleEvents
Expand Down Expand Up @@ -74,7 +75,7 @@ fdom.link.BackgroundFrame.prototype.setupListener = function() {
};

/**
* Set up an iBackgroundFrame with an isolated freedom.js context inside.
* Set up an iFrame with an isolated freedom.js context inside.
* @method setupBackgroundFrame
*/
fdom.link.BackgroundFrame.prototype.setupBackgroundFrame = function() {
Expand Down Expand Up @@ -109,7 +110,7 @@ fdom.link.BackgroundFrame.prototype.setupBackgroundFrame = function() {

/**
* Make frames to replicate freedom isolation without web-workers.
* iBackgroundFrame isolation is non-standardized, and access to the DOM within frames
* iFrame isolation is non-standardized, and access to the DOM within frames
* means that they are insecure. However, debugging of webworkers is
* painful enough that this mode of execution can be valuable for debugging.
* @method makeBackgroundFrame
Expand Down

0 comments on commit f5ba12e

Please sign in to comment.