Mac Zooming / clipping / drawing bug

NEW
Unassigned

Status

()

Core
XUL
16 years ago
8 years ago

People

(Reporter: Robert John Churchill, Unassigned)

Tracking

Trunk
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
Try this on Mac OS X:

o  open a browser window. Make sure it isn't in the zoomed state.
o  open the Find dialog
o  click the (now-behind) browser window's zoom box

What'll happen: the browser window will zoom, but the foreground Find dialog
will not draw its contents... you'll be left with merely a gray background.
(Reporter)

Comment 1

16 years ago
Created attachment 73627 [details]
Screenshot (JPEG format)

Comment 2

16 years ago
I can add that it's probably timing dependent: it doesn't happen to me every
time I zoom the browser window with Find open. In fact it seldom happens the
first time. Notice that it also happens (to me) with modal windows (sheets):
open the Open Location dialog and zoom up and down a few times. Dialog goes
blank gray.
(Reporter)

Comment 3

16 years ago
As far as I can tell, it isn't timing related... and seems to be more a function
of the dimensions of the background-about-to-be-zoomed browser window.  If you
make the browser window really small, open the Find dialog, then zoom the
browser window, it seems to clip (or draw to gray) the Find window based upon
the bounds of the pre-zoomed browser window.
(Reporter)

Comment 4

16 years ago
Hmmm... also, once the Find dialog has been "grayed"... merely mousing over the
elements in the dialog causes them to draw.

Comment 5

16 years ago
Still occurs using FizzillaCFM/2002061014. Guessing XP Toolkit/Widgets.
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doron → jrgm

Comment 6

14 years ago
Works for me in build 20040405 on Mac OS X 10.2.8. Reporter, is this still a
problem for you ?

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040405

Updated

9 years ago
Assignee: jag → nobody
You need to log in before you can comment on or make changes to this bug.