Closed Bug 263915 Opened 20 years ago Closed 19 years ago

double buffering for changing layers

Categories

(Toolkit :: Form Manager, enhancement)

x86
Windows 98
enhancement
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: peter.schaefer, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20040913 Firefox/0.10

Refreshing (big) div's with javascript sometimes causes flickering.


Reproducible: Always
Steps to Reproduce:
1. tell javascript to build a table 32x32 of images over a black tiled
background image(stars.gif)
2. refresh some div with debug output 
3. during 2.) randomly refill the table about 5-20 times/second.

Actual Results:  
Flickering. Not much, but suboptimal

Expected Results:  

IMHO It would be nice if FireFox switched on double-buffering for layers/div
that are repeatedly(the second time?!) changed by javascript. 
(Or if you could somehow switch this on manually. But i guess that would break
CSS/javascript standards).



It is not an issue of my PCs speed, since I emulated doublebuffering by using
two divs and switching the double buffer to the foreground by changing the
style.zIndex property. 

I guess it is a valid optimization to not use a doublebuffer, e.g. it saves
memory on small devices, but I'd find it nice.
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/
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
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.