bookmarks popup window need to be polished (versions from 1.4 to 1.8a1) on Linux platform



15 years ago
14 years ago


(Reporter: sherabpuntsok, Assigned: p_ch)



Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a1) Gecko/20040520
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a1) Gecko/20040520

Bookmarks popup window too wide (horizontally about 4/5 of the screen) after I
bookmarked a webpage by clicking on "Bookmark This Page" such as
causing other web titles under subfolders unviewable. This is not the case when
mozilla is running in Windows.

Reproducible: Always
Steps to Reproduce:
1. Bookmark a long URL web page (with no title) such as
2. Click on the Bookmarks button, the pop-up page will occupy about 4/5 of the
screen size.
3. Moving the mouse to other folders will pop-up the contents inside there, but
just displaying 1/5 in the rest of the screen causing it unviewable.

Actual Results:  
Bookmarks under sub-folders can not be read. (Work around: have to open the
Bookmark by clicking on "Manage Bookmarks...", and select the bookmarks inside
the folders)

Expected Results:  
Sub-folder contents can overlap the initial pop-up window and within the screen

OS: Debian Woody 3.0 r0 on Intel P4 1.6 gHz cpu with 512m ram
Display: Nvidia GeForce 2 400
Mozilla 1.8a1


Build platform

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 3.2.3 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align
-Wno-long-long -pedantic -pthread -pipe
c++ 	gcc version 3.2.3 	-fno-rtti -fno-exceptions -Wall -Wconversion
-Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -Wno-long-long -pedantic -fshort-wchar -pthread -pipe

Configure arguments
--disable-tests --enable-extensions=default,irc,tasks,negotiateauth
--without-system-nspr --without-system-jpeg --without-system-zlib
--without-system-png --without-system-mng --disable-debug '--enable-optimize=-O2
-gstabs+' --enable-crypto
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.