Whenever a form is loaded (as in the URL in this bug), or whenever a form with multiple input fields is scrolled, apprunner seems to redraw in a chunky manner that creates a visually disruptive behavior on the display (heck, it might even induce seizures in epileptics!). Basically, the rectangles that signify the form inputs are redrawn quickly and over existing rectangles so that you get a mess of rectangles on the screen. Once loading or scrolling is completed, everything does refresh okay, so this can probably be put off until post-dogfood.

Re-assigned to rickg@netscape.com and changed component to Layout.

Yo - mikey! It appears to be a legit scrolling bug, and you appear to be someone who may be interested. Either assumption may be wrong! :)

i don't see a problem today (with my fix checked in yeasterday)...

cpratt, Win32 build for Mar19 is out! Could you please mark this Verified today? Thanks!

Using the 9 am build, March 19, this isn't fixed as far as I can see. The best way to see what's going on? Load the page at the URL in this bug. While it's loading, watch as multiple rectangles are drawn that overlap each other. When it's finished loading, it looks fine... but then use the down arrow key to scroll down the page. Scroll up and down using the arrow keys and you should see what I'm referring to.

Actually, even better: Using the arrow keys, scroll down to the bottom of the page & then back up to the top. If you keep the up arrow key depressed, the browser will NOT refresh & you should see exactly what I'm referring to.

Putting on M3 radar for a possible Release Note. michaelp, thoughts?

oh, you need to use keys to scroll. that's useful information. i've never done that before and didn't even know you could. after looking at the code that deos the key handling, i've found that it's using a non-optimal code path to do it's work and yes, it can look a little ugly today. for now, don't scroll with keys or it'll look ugly. this will be fixed later. i still don't see anything that's not refreshed or "multiple rectangles are drawn that overlap each other." does this actually happen on windows? i know that mac is busted and does this, but i haven't seen this under NT, 95 or 98.

I'm using NT on a Vectra XA with a Millennium display adapter, and I'll try to describe this better: if you scroll down, then up, and continue to hold down the up arrow key, what you see is input controls that contain garbage in them. Outside of the input controls, everything looks just fine, but inside of them it's as if something had been drawn several times, which results in garbage. Radio button controls, for example, largely disappear. Unfortunately, I can't take a screen shot as I need to release the up arrow button to do so. If anyone around has a stock Netscape Vectra XA box, this behavior should be (hopefully) easy to reproduce. Mine is set to 1152 by 784, 32K colors.

still haven't seen the garbage painting, but it now blits rather than painting whenever possible in this case, so the garbage shouldn't appear anyways.

Well, something has changed in the 0930 March 22 build. It doesn't do the same thing it did before - it is now broken in a different way. I'm marking this as verified fixed and opening a new bug...

Actually, part of this problem has NOT been fixed, so I'm reopening this. The problem is this: when this URL is initially loaded, the text input controls contain garbage within them that is identical to the problem as originally decribed here. Other than that, the rest of the problems described in this bug have been fixed (but are now broken in different ways).

is this garbage text?

No, it isn't garbage text that's displayed inside of the controls while loading the page. It looks like horizontal lines (as if controls had been painted in the window, and then moved to the correct positions, but the old control rectangles had been left where they were before, and not erased when inside of newly-drawn rectangular controls). Hope that description helps...

tried with my current build and the daily build for today and all was well.

Looks fine (although there are problems with the URL control, opening separate bug for that) even on a very slow Pentium.