The default mozilla profile only have two direct links in the personal toolbar: "The Mozilla Organization" and "Latest Build" The link "The Mozilla Organization" seems to be cut off so it says: "The Mozilla Or..." even though that it has the entire toolbar to fill. Basicly "..." should only be added if there isn't any space to show the entire title.

spellcheck summary please...

themes?

Sorry, but this is a wontfix as far as themes are concerned. Personal toolbar buttons have a max-width on them so they don't hog up space. The only way to allow them to be wider if they have the room is to apply flex to them, but that has other undesirable visual consequences. The real problem here is that the personal toolbar has no way to display bookmarks that run of the edge of the window. We wouldn't need a max-width on these buttons if that were possible. IE has a very practical way of dealing with this -- a menubutton appears on the right end of the toolbar which displays the bookmarks that run off the edge.

There's no way to detect if a bookmark is gonna run "off" the screen?

IE's way of dealing with this bug has nothing to do with (bug 66919, bug 12759). IE's way of dealing with this is to not truncate titles. Why do Mozilla's personal toolbar buttons have a maximum width at all? Is it because it's currenlty too difficult to rename personal toolbar items (bug 17920) when extra room is needed? The maximum width should at least be increased to accomodate three-word titles (including one that is shipped as a default personal toolbar item!).

This is really a design feedback bug. We need a way to show bookmarks that run off the edge of the personal toolbar, and that will require some UI design. German, how do you think this should be handled?

updating to new owner. sorry for the spam.

From a usability perspective I like IE's 'left-overs' menu best, as the solution with having a taller toolbar (ie 2 'lines')leaves of lots of unsightly situations where items of different lengths do not line up. As a result n-line toolbar items will be much harder to find and parse. While we are brainstorming, here are some other crazy ideas: - add scroll buttons to either side in case of overflow - add autoscroll zones on either side like in menus, the toolbar would scroll back after having selected an item

RFE cleanup. RFE is already indicated by the Severity field...Sorry for the spam!

See also bug 150433, do not abbreviate bookmarks in personal toolbar if there are few enough.

uid is being phased out.

We now have an overflow widget on the personal toolbar. Does this mean we could make bookmarks take as much space as they want? I guess if the user ends up in a situation where the first bookmark's title is so long it doesn't fit on the toolbar (and in the process shoving off all other bookmarks / folders, leaving her with an empty PT), she'll hopefully realize this and edit it. Note that Safari crops bookmarks (in the center). IE for Mac doesn't crop, and has the "problem" I pointed out above.

*** Bug 150433 has been marked as a duplicate of this bug. ***

I complained about the truncation in comment 5, but now I'm finding the truncation useful. Maybe it should truncate if you've never edited the title. (That would require it to remember whether you've edited the title.)

not sure if this is a related problem, but i am getting the overflow widget, and bookmarks moved into it, even when my personal toolbar is less than 60% full. and they are very short titles that are going into overflow, not nearly long enough to go off the edge of the screen.

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420