Closed
Bug 268190
Opened 20 years ago
Closed 19 years ago
Incomplete painting when running Adobe Premiere Pro 1.5
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: kennu, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 When Adobe Premiere Pro 1.5 is running in the background (either minimized or maximized), Firefox has weird problems painting the screen. If the Firefox window is larger than about 1024x768, or maximized (1920x1200 on my desktop), it can't paint the current web page or the toolbar. They just "leak" the stuff from underneath them. This is probably releated to some special screen mode that Premiere is setting up for the system. Internet Explorer works, however. I noticed this bug because Premiere's help file is HTML and since my default browser is Firefox, I can't browse the help comfortably. Reproducible: Always Steps to Reproduce: 1. Start Adobe Premiere Pro 1.5 2. Start Mozilla Firefox 3. Open any webpage and maximize the browser window (with a large display, at least 1920x1200 will do) Actual Results: The webpage and Mozilla toolbar are not painted properly on the screen. They "leak" the graphics underneath them that should have been painted over. Expected Results: It should have worked as usual.
| Reporter | ||
Comment 1•20 years ago
|
||
(In reply to comment #0) It seems that this bug is not always reproducible. After rebooting the computer, it went away at least for now.
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•