Closed Bug 78350 Opened 24 years ago Closed 24 years ago

"Enter key" not working when typing URL in URLbar

Categories

(SeaMonkey :: Location Bar, defect)

Product:
SeaMonkey
Component:
Location Bar
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 78243

People

(Reporter: doctor__j, Assigned: hewitt)

Details

(Keywords: regression, smoketest)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.8.1+) Gecko/20010430 BuildID: 2001043020 Reproducible: Always Steps to Reproduce: 1. Close all Mozilla browsers. 2. Load Mozilla browser. 3. You should see cursor blinking at URLbar. 4. Type some URL. Any URL will do. 5. Press "Enter". Actual Results: Mozilla has no reaction to your "Enter key". URL isn't loaded. Expected Results: Moz should start loading the URL. Bug occurs on any theme, not only on Modern3 theme.
Confirming with win2k build 20010501.. (CVS 08 AM) I can´t hit enter in the URLbar. The little drag icon in the URLbar disappears if I write the first letter in the URL bar.
Severity: major → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression, smoketest
updating severity
Severity: critical → blocker
No problem in build 2001032614 on GNU/Linux i386.
Confirm in build 2001-04-30-21 and 2001-05-01-morning.
That is Linux-SuSE-7.0, builds 04-30 evening and 05-01 morning.
This only occurs before you go to the first page (eg if you have a homepage you will never see this bug). *** This bug has been marked as a duplicate of 78243 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Boris: I see this the whole time and I have a home peage (local file) reopening
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
i saw it on linux too, but after deleting component.reg, URL bar again accepted input. Autocomplete on Linux is completely horked though. Doesn't complete anything but spews out: Gdk-CRITICAL **: file gdkwindow.c: line 716 (gdk_window_ref): assertion `window != NULL' failed. Seems it wants to search google instead of autocompleting? In addition, mousing over the now forever empty autocomplete dropdown area, i get pagefulls of these in console: JavaScript error: chrome://global/content/autocomplete.xml#autocomplete-outlinerbody.getHoverCell() line 7: obox has no properties
-> hewitt
Assignee: alecf → hewitt
Status: REOPENED → NEW
*** This bug has been marked as a duplicate of 78243 ***
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
forget earlyer comment - horkage is my own.
VERIFIED Dupe
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.