256432 - File bookmark box does not open fully

Status: RESOLVED DUPLICATE of bug 248958

(SeaMonkey :: Bookmarks & History, defect)

Description

[carljordan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040820
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040820

When I use Bookmarks|File Bookmark, the box that opens does not go down far
enough to expose the three buttons.  I manufally adjust it, though, with no
problem.  This only occurs on one of my installations, the one in my office, not
the one in my home.  It has been constantly that way.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Actual Results:  
File bookmark box not fully extended downward.

Expected Results:  
Expect file bookmark box to extend downward sufficiently to show the three buttons.

Comment 1

[Hermann Schwab]

If you adjust the size of the box, it should be remembered in the profile, so no
need to repeat this procedure in your next browsing session.
Your are seeing this bug at work, not at home.
Maybe you don´t have write access to your profile folder, or there are locked
preferences?
Did you, or a colleague, install mozilla yourself, or do you have a standard
installation from the IT department?

Comment 2

[carljordan]

I installed it myself.  I've never changed my profile, at least knowlingly.  Our
official browser is IE, but I only use it when I absolutely need to.  I'm in a
Fed. Govt. office, and I do have administrative rights on my computer. 
 
In lprefs.js (last modified 9.2.02) I have a line that reads:
user_pref("browser.bookmark_window_showwindow", 3);

In prefs.js (last modified 8.23.04) I have the following lines:
user_pref("browser.bookmark_columns_win", "v1 1 1:10000 2:2996 4:1999 3:1999");
user_pref("browser.bookmark_window_rect", "118,32,600,411");
user_pref("browser.bookmark_window_showwindow", 3);

It looks like the same in prefs-1.js (last modified 7.23.04):
user_pref("browser.bookmark_columns_win", "v1 1 1:10000 2:2996 4:1999 3:1999");
user_pref("browser.bookmark_window_rect", "118,32,600,411");
user_pref("browser.bookmark_window_showwindow", 3);

Nothing about bookmarks in my user.js file.

Perhaps I have to change one or more of these settings, but I would not know
which one.

When I expand it by dragging down the bottom to see the three buttons, it does
not retain that setting.

TIA.

Comment 3

[Hermann Schwab]

You can also view&change these settings via about:config
http://www.mozillazine.org/misc/about:config/
I´ve got 
browser.bookmark_window_rect          user set  string   -12,174,600,411
browser.bookmarks.added_static_root   user set  boolean  true

If you want to see the bookmarks settings only, type bookm into the filter line

I reduced the height, increased the width, and moved the position of the dialog,
and restartet the browser. The settings for the dialog persisted, the
about:config settings remained unchanged.

The positions for windows are in localstore.rdf in your profile, and there have
been changes.

search for 'addb' in your localstore.rdf:

<RDF:Description
RDF:about="chrome://communicator/content/bookmarks/addBookmark.xul#newBookmarkDialog"
                   screenX="40"
                   screenY="82" />
  <RDF:Description
RDF:about="chrome://communicator/content/bookmarks/addBookmark.xul">
    <NC:persist
RDF:resource="chrome://communicator/content/bookmarks/addBookmark.xul#newBookmarkDialog"/>
    <NC:persist
RDF:resource="chrome://communicator/content/bookmarks/addBookmark.xul#bookmarks-view"/>
  </RDF:Description>
 <RDF:Description
RDF:about="chrome://communicator/content/bookmarks/addBookmark.xul#bookmarks-view"
                   colinfo=" col:Name?width=&amp;hidden=&amp;ordinal=1"
                   height="184"
                   width="692" />

these lines are unique, but at different places. They change places, as this
file is updated when you change positions and/or sizes.

Do you have the NC:persist lines?
Is your localstore.rdf updated?

Do you use themes and extensions?
(I´m using the classic theme)

Comment 4

[Peter Weilbacher]

As bug 248958 was filed earlier and has more recent comments I dupe this one...

*** This bug has been marked as a duplicate of 248958 ***