Closed
Bug 141394
Opened 23 years ago
Closed 22 years ago
location field corrupted after following a link
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: brion, Assigned: Matti)
References
()
Details
Attachments
(1 file)
147.57 KB,
image/jpeg
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.12 i386; Nav)
BuildID:
If I open a blank browser window, go to a web page, and follow a link,
then the location field will try to behave like a textarea; the
scroll bars will take over the whole thing rendering it unusable.
Reproducible: Always
Steps to Reproduce:
1.Build mozilla 1.0RC1 from the FreeBSD ports tree (cd /usr/ports/www/mozilla;
make install)
2. Launch mozilla. Start page is blank.
3. Enter any URL. Say, www.mozilla.org.
4. Click on any link. The next page will come up, but the location field is now
ruined.
Alternate step 3: enter a search term in the location bar, click "search".
Actual Results: location bar is hosed
Expected Results: normal location bar
browser version:
Mozilla 1.0 Release Candidate 1
Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020429
uname -a:
FreeBSD congerie 4.3-RELEASE FreeBSD 4.3-RELEASE #0:
Fri Jun 29 17:05:51 PDT 2001 root@congerie:/usr/src/sys/compile/GOOSE i386
FreeBSD port mozilla-1.0.rc1,1
Reporter | ||
Comment 1•23 years ago
|
||
To get this state I just opened mozilla, typed "mozilla" in the location field
and clicked "search".
Do you see this on a fresh new profile too?
Not least: Have you added this to your current prefs.js:
user_pref("nglayout.widget.gfxscrollbars", true);
I don't know what the freeBSD ports tree midd add, but if you do NOT have the
line above in prefs.js: does adding this line cure it:
user_pref("nglayout.widget.gfxscrollbars", false);
Suspecting dup of bug 141495
Reporter | ||
Comment 3•23 years ago
|
||
Adding a new profile does cure it. My existing profile, if it matters, is
imported from Netscape 4.
My user_prefs file has
user_pref("nglayout.widget.gfxscrollbars", false);
I didn't add it deliberately...that setting has been there all along, as far as
I can tell.
If I change it to true, then I do not have the problem.
Reporter | ||
Comment 5•23 years ago
|
||
No, never. I use it on Redhat and Win2K at work, but at home just on FreeBSD.
The user profile under which I encountered this bug was never used on any platform
other than FreeBSD.
user_pref("nglayout.widget.gfxscrollbars", true); has been in all.js for years,
according to lxr blame log. Do you know how and when the "false" setting land in
your user_prefs? I can't remember seeing it there ever in my own setup, so i
doubt it's a deafult.
Reporter | ||
Comment 7•23 years ago
|
||
I didn't change it manually...I've been running Mozilla since 0.8.1 or so,
so it's entirely possible that I still had the setting from some really old
version. I never had the scrollbar problem before 1.0rc1, though.
Assignee | ||
Comment 8•22 years ago
|
||
Reporter: Is this a problem with mozilla1.1b ?
Comment 9•22 years ago
|
||
No response
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•