remove some comments about tile manager
authorBenjamin Stover <bstover@mozilla.com>
Wed, 25 Aug 2010 10:48:26 -0700
changeset 1958 ad1da0d06b0460a00e422d6b132cf2d989116228
parent 1957 10225d8ae17d093263c147fd71391e2cf2543870
child 1959 3141a5efd6b8ee35a3c6e04f1ccf97edcf5c2af0
push id1714
push userdougt@mozilla.com
push dateThu, 16 Sep 2010 02:04:21 +0000
remove some comments about tile manager
chrome/content/BrowserView.js
--- a/chrome/content/BrowserView.js
+++ b/chrome/content/BrowserView.js
@@ -65,20 +65,17 @@ const kBrowserViewZoomLevelPrecision = 1
  *     and height persist across setBrowser() calls.  This is best explained by
  *     a simple example: user views browser A, pans to position (x0, y0), switches
  *     to browser B, where she finds herself at position (x1, y1), tilts her
  *     device so that visible rectangle's width and height change, and switches
  *     back to browser A.  She expects to come back to position (x0, y0), but her
  *     device remains tilted.
  * - Critical (the implicit one): The critical rectangle is the (possibly null)
  *     intersection of the visible and viewport rectangles.  That is, it is that
- *     region of the viewport which is visible to the user.  We care about this
- *     because it tells us which region must be rendered as soon as it is dirtied.
- *     The critical rectangle is mostly state that we do not keep in BrowserView
- *     but that our TileManager maintains.
+ *     region of the viewport which is visible to the user.
  *
  * Example rectangle state configurations:
  *
  *
  *        +-------------------------------+
  *        |A                              |
  *        |                               |
  *        |                               |
@@ -120,22 +117,16 @@ const kBrowserViewZoomLevelPrecision = 1
  *        |                               |
  *        |                               |
  *        +-------------------------------+
  *
  *
  * A = viewport ; at (0, 0)
  * B = visible  ; at (x, y) where x < 0, y > 0
  * C = critical ; at (0, y)
- *
- *
- * Maintaining per-browser state is a little bit of a hack involving attaching
- * an object as the obfuscated dynamic JS property of the browser object, that
- * hopefully no one but us will touch.  See BrowserView.Util.getViewportStateFromBrowser()
- * for the property name.
  */
 function BrowserView(container, visibleRectFactory) {
   Util.bindAll(this);
   this.init(container, visibleRectFactory);
 }
 
 
 // -----------------------------------------------------------
@@ -480,10 +471,9 @@ BrowserView.BrowserViewportState.prototy
   toString: function toString() {
     let props = ["\tviewportRect=" + this.viewportRect.toString(),
                  "\tvisibleX="     + this.visibleX,
                  "\tvisibleY="     + this.visibleY,
                  "\tzoomLevel="    + this.zoomLevel];
 
     return "[BrowserViewportState] {\n" + props.join(",\n") + "\n}";
   }
-
 };