Bug 87540 - nsImageFrame was offsetting invalidate rect by one pixel

for historical reasons (jpeg decoder used to one-index update rect).
r=kmcclusk, sr=blizzard
This commit is contained in:
tor%cs.brown.edu 2001-06-25 22:14:37 +00:00
parent bdec5a3e6c
commit 25c43a19d0
2 changed files with 0 additions and 18 deletions

View File

@ -324,15 +324,6 @@ NS_IMETHODIMP nsImageFrame::OnDataAvailable(imgIRequest *aRequest, nsIPresContex
nsRect r(aRect->x, aRect->y, aRect->width, aRect->height);
/* XXX Why do we subtract 1 here? The rect is (for example): (0, 0, 600, 1)..
Why do we have to make y -1?
*/
// The y coordinate of aRect is passed as a scanline where the first scanline is given
// a value of 1. We need to convert this to the nsFrames coordinate space by subtracting
// 1.
r.y -= 1;
float p2t;
aPresContext->GetPixelsToTwips(&p2t);
r.x = NSIntPixelsToTwips(r.x, p2t);

View File

@ -324,15 +324,6 @@ NS_IMETHODIMP nsImageFrame::OnDataAvailable(imgIRequest *aRequest, nsIPresContex
nsRect r(aRect->x, aRect->y, aRect->width, aRect->height);
/* XXX Why do we subtract 1 here? The rect is (for example): (0, 0, 600, 1)..
Why do we have to make y -1?
*/
// The y coordinate of aRect is passed as a scanline where the first scanline is given
// a value of 1. We need to convert this to the nsFrames coordinate space by subtracting
// 1.
r.y -= 1;
float p2t;
aPresContext->GetPixelsToTwips(&p2t);
r.x = NSIntPixelsToTwips(r.x, p2t);