Reproduction Path: From the google page. Type a textual query into the search box on the page that is longer than can be displayed in the box. Error: When the text reaches the end of the box the box fails to render the textual scrolling properly. Moving the cursor within the box using the arrow keys exacerbates the problem, to the point that determining what was typed becomes virtually impossible. Regression: It seems that all of the text is getting entered in. If the first part of the text is deleted so that the remaining text fits within the box, this text will display properly and moving the cursor with the arrow keys works fine. This only seems to happen when the text exceeds the box's width. Further Discussion: This behavior is also observeable in the Location box at the top of the page, and proves very problematic with long urls especially with sites that use long query strings. I'm assuming that the Location box and the text box on the google site are the same controls and that this is therefore the same problem. If not please let me know and I will write up the bug in the location box.

Yes, I am seeing this on linux too. Win32 looks Ok. Kin? Pavlov? Editor. P2.

clearing bogus CC list, that was my test case :-)

Accepting bug, setting milestone to M12. Do things scroll properly if you enable Gfx scrollbars? If so, this is a bug in the gtk implementation of nsScrollbar::SetPosition() (bug #13407 assigned to pavlov@netscape.com). To enable Gfx scrollbars, add the following line to your ~/.mozilla/<username>/prefs.js file: user_pref("nglayout.widget.gfxscrollbars", true); and restart your browser.

Added mcafee, akkana, and pavlov to the Cc list.

Putting on PDT+ radar.

Updating QA Contact.

*** Bug 17804 has been marked as a duplicate of this bug. ***

Adding a dependency on bug #13407. The problem is the same, but the symptoms are different. 13407 is reproduced by selection auto-scrolling, this one by typing.

linking to PDT+ bug

FYI, this bug will be fixed when 13407 is fixed, or we switch over to using GFX scrollbars.

Kin we need to get this bug fixed. Are gfx scrollbars working well for you? If so I'm going to turn them on by default.

Yes, Gfx scrollbars are working pretty good in my source tree. I'll send out diffs for a code review today so I can check it in either today or tomorrow.

I checked in changes to get selection auto-scrolling working with Gfx scrollbars. This means we can now make Gfx scrollbars the default.

evaughan@netscape.com will be enabling Gfx Scrollbars by default today, so builds starting on 11/24/99 should not exhibit this bug unless native scrollbars are enabled.

*** Bug 19516 has been marked as a duplicate of this bug. ***

*** Bug 19915 has been marked as a duplicate of this bug. ***

gfx scrollbars are on by default, can we mark this fixed?

Now that gfx scrollbars are in by default, this issue resolved if the users choosies to utilize gfx scrolling. However, if the users chooses to use gtk scrollbars this is still an issue. The gtk issue is bug 13407. Since fixing 13407 resolves this issue, marking this as a dup of 13407. Although the symptoms seem different in both bugs, they both go through the same code path. *** This bug has been marked as a duplicate of 13407 ***

verified in 11/29 build.

*** Bug 18583 has been marked as a duplicate of this bug. ***

*** Bug 21058 has been marked as a duplicate of this bug. ***

*** Bug 22124 has been marked as a duplicate of this bug. ***