User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 The current history, bookmarks and download managers look dated and not very integrated with the browser experience. Especially now that the Add-ons manager is modified into a browser tab based interface I think these components should be part of it too (perhaps with the ability to set them as App-tabs for easy access). This would make them a much more integrated part of the browser experience. Reproducible: Always

I do not think so, especially history and bookmarks manager(Library). If Library is displayed in a tab, * I can not open Bookmark/history in new tab foreground from Library continuously. * I can not drag&drop link of web page to the Library without switing tab. I think that the library should be displayed as an independent window.

Dear Alice, I am only suggesting to have the same behavior as the new Add-ons manager which is by default displayed like a nice and modern looking (presumably HTML5) app in a tab. You can always make it into an independent window by simply dragging the tab out of the tab bar (as with any other tab). This way both our desired behavior is possible, right now it's only yours :)

>You can always make it into an independent window by simply dragging the tab >out of the tab bar (as with any other tab). Open Bookmark in New Tab from the detached window(Library), it will open in the detached window, not the original window.

This is planned at some point, see https://wiki.mozilla.org/Firefox/Projects/Incontent_Page_Design and http://blog.stephenhorlander.com/2010/06/01/in-content-ui-visual-unification/ Since there wasn't a tracking bug already, confirming this one.

This may be easily done with a few lines of code. Perhaps there could be an about:config option to disable it.

This would be great, I don't like the combination of the new awesome addons manager against history and bookmarks still in a separate window personally, I don't see why there can't be about:history and about:bookmarks for Firefox 4 after all these changes (Chrome already does it, and it works out well).

is this planned for firefox 5 ?

(In reply to comment #7) > is this planned for firefox 5 ? I don't think that its planned for anything at the moment. There's been a severe lack of activity on In-Content projects in Bugzilla.

(In reply to comment #7) > is this planned for firefox 5 ? Firefox releases are no longer feature orientated, so while previously things were planned for a specific version. The current release model means that a release could feature nothing other than stability and security improvements. What that means for features like ICUI is that if it's not ready at the time of a release, it won't make it in. Being that there are so few patches being submitted for this and Mozilla resources are tied up elsewhere, this could in fact never happen or Firefox 15 may come out before there's a chance to focus on this. Ultimately patience is the key unless you have the skill-set to work up a patch yourself.

Than perhaps it would be nice to have a page where users can suggest features and other users can vote for them so Mozilla developers can prioritize and external developers have an idea which project to take on. Mozilla could even tag some features as being better suited for extensions which would give extension developers an indication of what to tackle next.

(In reply to comment #10) > Than perhaps it would be nice to have a page where users can suggest features > and other users can vote for them so Mozilla developers can prioritize and > external developers have an idea which project to take on. Mozilla could even > tag some features as being better suited for extensions which would give > extension developers an indication of what to tackle next. If an external develop is new to bugzilla and would like to patch their first bug, a good place to start would be the pre-marked bugs for that exact purpose: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%22[good%20first%20bug] More advance developers that would like to specifically work on Firefox bugs can check here: https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=NEW&version=Trunk&product=Firefox&product=Toolkit IF an end user would like to show support for a specific bug, you can always use the voting system. Subscribing to the bugs gives an oversight, but the official best method is to start a thread on the usergroups. In regards to features that would be better as extensions, that's mostly a subjective stance to take. While something might work better as an extension for a specific set of users, for more it might be a case of that should just be built in. Firefox has always endeavoured to provide closer to the minimum for what it takes to enjoy the internet comfortably and as such has garnered such a huge library of add-ons providing more usability. Even Chrome which was once seen as a more alternative bare-bones browser has started to match the features of Firefox despite the opposition Firefox received from its power-users against such features.

> IF an end user would like to show support for a specific bug, you can always > use the voting system. Subscribing to the bugs gives an oversight, but the > official best method is to start a thread on the usergroups. Seriously, do you expect the average end user to do this? I know experienced users or fellow developers can always report or vote on bugs. But how about the average non-developer user? I don't see what could possibly be wrong with a easily accessible (e.g. not bugzilla but something more like stack overflow) website where the average end user can give suggestions or vote on existing ones. Especially when development is no longer feature driven I think there is a risk of features in high user demand never getting implemented.

(In reply to comment #12) > > IF an end user would like to show support for a specific bug, you can always > > use the voting system. Subscribing to the bugs gives an oversight, but the > > official best method is to start a thread on the usergroups. > > Seriously, do you expect the average end user to do this? I know experienced > users or fellow developers can always report or vote on bugs. But how about the > average non-developer user? I don't see what could possibly be wrong with a > easily accessible (e.g. not bugzilla but something more like stack overflow) > website where the average end user can give suggestions or vote on existing > ones. > Especially when development is no longer feature driven I think there is a risk > of features in high user demand never getting implemented. Firefox 4 came bundled with a feedback extension. You can always use that to give feedback including requests for feature enhancements.

I know and I like the feedback extension. It is just kind of hard to track what subsequently happens with these suggestions and what other people think of them. This is far more easily done by submitting feature requests (like this one) here on bugzilla. I would like to see something in between. I for one get a bit nervous from the following: > Firefox releases are no longer feature orientated, so while previously things > were planned for a specific version. The current release model means that a > release could feature nothing other than stability and security improvements. > What that means for features like ICUI is that if it's not ready at the time of > a release, it won't make it in. Being that there are so few patches being > submitted for this and Mozilla resources are tied up elsewhere, this could in > fact never happen or Firefox 15 may come out before there's a chance to focus > on this. Ultimately patience is the key unless you have the skill-set to work > up a patch yourself. while I welcome a faster release schedule and think the "what is in the next release is whatever happens to be ready" is a decent approach for that, I do think there should be some way for non-developers to influence what will be likely to make it first.

As originally filed, this is a duplicate of bug 697359. We're going to do development in that bug, so there is no further need for this one. View Source and Options in a tab are separate issues that don't really need to be put together with this.

I thought we was meant to dupe to the oldest existing bug and copy the CC list across?

Bringing config / control of an application like the matter handled by the application is *a bad idea*, a fad à la Google Chrome. It has security implications. For the basic user, clicking stuff in a tab is playing with a page, so it is pretty safe, it is not changing the settings of the browser itself. Contrary to acting in a real window / dialog of the application. Actually, when I open some preferences, like the add-ons manager, I expect it to come as a front window / dialog, I hate when it opens a new tab mixed with the navigation tabs. It controls the behaviour of the whole browser, so I expect a window or a dialog, like the preferences window. Furthermore, this preferences dialog must have at most one existence. As a tab, what if I leave it and later, when I'm in another window, I request it ? It opens as a second occurrence ? Awkward. Or Firefox brings the old window ? And if its some-stuff-manager tab was in the background, it puts it to the foreground ? And then, when I close it, I land not only in a different tab than I was before, but even in a different window. Bad, disturbing user experience. Furthermore, there are a bunch of annoying scenarios in Firefox tab behaviour where closing a tab does not bring you in the tab you were in just before. Same goes for the Downloads manager. As this too : I have many windows with many tabs. I want the Downloads window. I go, on Mac, to the Windows menu - called Fenêtres in French, so not so much an OS paradox ;-) - and I choose Downloads. I get the Downloads window. I leave it open and I go navigating in my windows and tabs... Later, I want it again, I find it easily in the list of windows. If it is a tab deeply sunken somewhere, how do I find it ? And if the menu finds it for me and puts it in front of me, that brings the disturbances previously mentioned. Config / control stuff is not navigation, this should not interfere with the user's navigation flow.