Closed Bug 260862 Opened 20 years ago Closed 20 years ago

Focus on URL drop widget is off

Categories

(SeaMonkey :: General, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: marcia, Unassigned)

References

Details

Seen on today's trunk build, Mozilla 1.8a4 Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a4) Gecko/20040921 I have also confirmed that this bug exists on Windows XP and Linux. STR: 1. Click on the URL drop widget (after several browser sites have been visited) 2. Observe that nothing happens (on the Mac the drop widget disappears - poof!) 3. If you click on the dropdown and then move your cursor slightly to the right, the URL dropdown list appears. On Windows and Mac you actually are on the "Search" button when you do this.
nominating for blocking 1.8a4
Flags: blocking1.8a4?
could this be a regression (if so, perhaps related to bug 260821 or bug 260717)?
not sure if this is related, but I noticed something nearly similar with the Tabs dropmenu in the Sidebar: 1. open the Sidebar. 2. open the Tabs dropmenu in the Sidebar and select Customize; the Sdiebar customization dialog does appear, but so does this js error: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIRDFService.GetResource]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://communicator/content/sidebar/sidebarOverlay.js :: SidebarTogglePanel :: line 1290" data: no] 3. hit cancel to dismiss the customize dialog. 4. try to open the Tabs dropmenu again. results: no dropmenu appears. tested with 2004092107-trunk (seamonkey) bits on linux, while fiddling with the smoketest case: http://testrunner.mozilla.org/test.cgi?run_id=452#17 please let me know if a separate bug should be filed.
OS: MacOS X → All
also see this with the column picker, which occurs throughout the suite (at the top of the thread pane in the mailnews 3pane window, in the Search Messages dialog, bookmarks manager, etc). aaronl, do you think this and the above issues could've been caused by your fix in bug 68841? if yes, could they have been fixed for your patch in bug 260657?
(In reply to comment #4) > aaronl, do you think this and the above issues could've been caused by your fix > in bug 68841? if yes, could they have been fixed for your patch in bug 260657? Doesn't sound related.
Depends on: 260657
Fixed by checkin for bug 260657
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
no longer able to repro the case in comment 3 with 2004092207-trunk bits on linux fedora core 1.
Flags: blocking1.8a4?
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.