Closed
Bug 313178
Opened 19 years ago
Closed 18 years ago
canvas drawWindow fails to draw anything when window is scrolled past a certain point
Categories
(Core :: Graphics: Canvas2D, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ted, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
860 bytes,
text/html
|
Details |
See attached testcase. If the window is scrolled past 299, and you call cx.drawWindow(w,0,0,300,300,"rgb(255,255,255)"); nothing is drawn in the canvas. This breaks the usefulness of drawWindow, although you can work around it by increasing the height of the area you draw. For example: cx.drawWindow(w,0,0,300,w.innerHeight+1,"rgb(255,255,255)");
Reporter | ||
Comment 1•19 years ago
|
||
Testcase showing drawWindow behavior (requires UniversalBrowserRead)
Reporter | ||
Comment 2•19 years ago
|
||
Looks broken on trunk too.
Actually, this works for me on trunk. Could it be Windows only?
Reporter | ||
Comment 4•19 years ago
|
||
I just tested with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051020 Firefox/1.6a1 and it still doesn't work for me. Are you using a tinderbox build or your own?
It's my own build, but it's not patched.
I can reproduce this.
Reporter | ||
Comment 7•19 years ago
|
||
Less CNN, more solid color div. Same bug.
Attachment #200248 -
Attachment is obsolete: true
Reporter | ||
Comment 8•18 years ago
|
||
This WFM in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060130 Firefox/1.6a1 I bet frame display lists fixed it.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Comment 9•17 years ago
|
||
Im not sure it was actually since this appears to be fixed on 1.8.1 branch as well as trunk. Anyway thats useful info for those that need it.
Comment 10•17 years ago
|
||
(In reply to comment #9) > Im not sure it was actually since this appears to be fixed on 1.8.1 branch as > well as trunk. Anyway thats useful info for those that need it. Was this very recently fixed on the branch (that seems unlikely to me)? I still see the problem in FF 2.0.0.3 on WinXP.
You need to log in
before you can comment on or make changes to this bug.
Description
•