Bug 556174 (FirefoxButton)

[meta][project] Firefox Button

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
9 years ago
3 years ago

People

(Reporter: faaborg, Unassigned)

Tracking

({meta})

Firefox Tracking Flags

(Not tracked)

Details

()

Attachments

(1 obsolete attachment)

This is a meta tracking bug for the project of replacing the traditional menu bar with a single high contrast application level button on Windows Vista and 7.  The traditional menu bar will still be available as an option (but not the default), and alternatively the Firefox button will be available on XP as an option (but not the default).

Initial work on the design and some analysis of usage is available here: http://blog.mozilla.com/faaborg/2010/03/23/visualizing-usage-of-the-firefox-menu-bar/

The Firefox button has been appearing in the mockups of the new windows theme for several months now, but this project will cover actually implementing it and getting it landed on trunk.
(In reply to comment #0)
> The Firefox button has been appearing in the mockups of the new windows theme
> for several months now, but this project will cover actually implementing it
> and getting it landed on trunk.
Which will be when exactly? As far as I know, FX button should be in beta 1, which should be out in june. That means:
1. It wont be in Beta 1
2. Beta 1 wont be in june
3. Both (which, by looking how far "progress" is, is more likely)
(In reply to comment #1)
> Which will be when exactly?

Obviously we can't know exactly when, but if you'd like to know their estimate then see the timeline -- https://wiki.mozilla.org/Firefox/Projects/New_Theme/Timeline

Things may be pushed, but no point in making assumptions.
That was a rhetorical question.
According to the timeline, work should be starting on this in a couple days, so everything is running to schedule.
Yeah, SHOULD. I don't see any evidence of any work at all.
Be patient. There are thousands of more important UI bugs that the developers are working on. If you're so eager for this to be done quickly, why don't you work on it؟
Believe me, if I could, this would bo done by now.
I'm not complaining that it isn't finished (I will, but aftwer weeks). But this is meta bug, which means there will be several depending bugs. It will be nice at least to create them and asigne them, so we can see that something is happening. Bug 513162 is good example of that.
I'll be filing all of the dependent UI bugs and getting a first draft of the design posted this week. We've been holding until we have the platform capability to draw in the title bar (bug 513162).
Depends on: 513162
And we do have it now?
(In reply to comment #9)
> And we do have it now?

Only for Mac.
Yeah, well, Mac isn't going to have Firefox button, so there is no point to asking if we have ability to draw in title bar for mac, don't you think?
(In reply to comment #11)
> Yeah, well, Mac isn't going to have Firefox button, so there is no point to
> asking if we have ability to draw in title bar for mac, don't you think?

FYI, While that's a fair comment, it does come across as a little overtly aggressive.
It wasn't my intetion to make it agressive.
(In reply to comment #13)
> It wasn't my intetion to make it agressive.

Then please be careful how you word things in future, and keep in mind that this will get done. It may take longer than expected, but it will. There's no need to pester the developers.

It's also spam. (Apologies to everyone on the CC list.)
This is a very initial take on the potential organization of the Firefox button.  Dao: if you want to get started with implementation this should be pretty close to what we want in terms of functionality:

1) non-native main panel with split button controls (clicking directly on the item carries out the main command)
2) main panel has two areas, Firefox commands on top, and extended functionality below (where developer is set as the only item in the extensions area by default).
3) All sub-menus are native (not represented all that well in this mockup, I didn't style them yet to match Windows).

We could start by getting the panel and sub menus working from a target that is placed in the normal toolbar, if we want to start implementation work before we get the ability to draw in the title bar.
Also note that the share link menu is purely hypothetical, by default we would start with just email and then might expand on this over time (and which services we might choose to include would obviously involve a lot of thought).
Well, Firefox menu will be useless in Ubuntu 10.10 and later, because they are going to implement Mac-like global menu.
This bug is windows vista/7 only, but for Ubuntu's netbook edition (are they also considering the global menu for desktop?) we will likely see an approach similar to our current UI on OS X.
sorry, forgot to set the platform
OS: All → Windows 7
Peter, please refrain from posting your own opinions & complaints in this bug. It just spams everyone, and adds nothing to the conversation. If you want to have a discussion around this, we're happy to do so on the dev.usability mailing list, but please keep this bug for implementation details and actual development discussion. :)
I'm not posting my own opinions and certainly not complaints. I just stated simple fact from Mac theme observation. What is bad on that?
By the way, Alex, global menu will be availible on desktop version too. Will be there widget which will determine if it is enabled? Or perhaps option to hide Firefox menu?
Depends on: 570795
Depends on: 571750
Depends on: 571752
Depends on: 571781
Depends on: 571782
Depends on: 571783
Depends on: 571784
Depends on: 571785
I should say that in the Print... menu entry, we should include a Print... child, just like the parent (and I know that you can click the parent for the same functionality), just to cover for those who won't be able to find out that they are supposed to click the parent if they want to Print... You know, make it behave like the Help entry, where you have the Help parent and the Help child.

This is, of course, relative to the early draft submitted by Faaborg.
I noticed that right now, the button is just out there wasting space on the top. Think we could for now just make it flush alongside the tab bar?
Is it possible to allow item icon like Download and Print to be placed in the space beside the Firefox Button?
(In reply to comment #24)

I think that will be implemented in beta 2.
Depends on: 572312
Depends on: 572413
Now that the button's up in the titlebar, shouldn't it be tweaked to match the mockup ( https://wiki.mozilla.org/File:Firefox-4-Mockup-i06-(Win7)-(Aero)-(TabsTop).png ) with the square corners on top, flush with the edge of the window?
Depends on: 574681
(In reply to comment #26)
> Now that the button's up in the titlebar, shouldn't it be tweaked to match the
> mockup (
> https://wiki.mozilla.org/File:Firefox-4-Mockup-i06-(Win7)-(Aero)-(TabsTop).png
> ) with the square corners on top, flush with the edge of the window?

I think the issue that you are talking about is being handled in Bug 571784. You should voice your question there.
Nope, that is Bug 574681.
Depends on: 574337
Depends on: 574928
Depends on: 575049
Depends on: 575088
Depends on: 575027
Depends on: 574973
Depends on: 575200
Depends on: 575166
Depends on: 575305
No longer depends on: 575305
Depends on: 575557
Blocks: 575166
No longer depends on: 575166
No longer blocks: 575166
just curious about when the menubar will be hidden for linux because at this point i have two locations to get bookmarks. also, i find that the menubar wastes a lot of screen real estate. 
the mockups for version 4 on linux look awesome btw.
You can easily hide the menubar yourself: right click on a toolbar or menubar, and unselect the menubar. It will reappear when you press Alt.
Unless what you meant was hidden by default, then you will have to wait for a while. There is no bug handling it yet.
We've gone back and forth on what the default for Linux should be a few times, the native precedent is for a traditional menu bar, but at the same time a lot of users would prefer a simpler default interface for their browser, even if it means breaking native conventions.  Either way there should be only one place to access bookmarks.
Depends on: 575726, 575451
Depends on: 575715
Depends on: 575291
Depends on: 575487
Depends on: 575598
Depends on: 576093
Depends on: 576312
Depends on: 576825
Depends on: 577283
Depends on: 577382
Depends on: 577900
Depends on: 577970
Note that when removing the Work Offline option, Bug 87717 should be fixed, because otherwise accessing your local webserver gets really complicated if there is no internet.

I have a local webserver on my notebook and constantly lose connection to it, just because my internet goes offline. Very annoying behaviour. And it will get much more annoying, if you have to make the menubar everytime visible to access the work offline button.
Jonathan, Not sure about the status of Work Offline now, since there is a bug about removing it altogether, See Bug 565564. 

Anyway I think Work Offline should be in the Firefox Menu so that Users can use them. See Bug 578009.
Depends on: 578009
Depends on: 578620
Depends on: 575271
Depends on: 578729
Depends on: 578611
Depends on: 578844
Depends on: 579278
Depends on: 579325
Depends on: 579371
I have a whole lot of bug filing to do (and sorting through all of the current dependent bugs).  But just to update everyone in real time, here are some very fresh mockups for the contents of the Firefox button, how we may transition commands, and some usage projections:

http://blog.mozilla.com/faaborg/2010/07/18/details-about-the-firefox-button/
I can't find "Check for updates..." item from Help submenu.
(In reply to comment #36)
> I can't find "Check for updates..." item from Help submenu.

That button is only useful for nightly users. However, that's the sort of thing that we should be discussing in the news groups.
(In reply to comment #36)
> I can't find "Check for updates..." item from Help submenu.

"Troubleshooting information, release notes and check for updates are located inside of the About window.
Interesting. I'd like to see mockup of that as well.
Bug 571781 has not landed hence no Help sub-menu.
Qestion for Alex: This styling is global?
You mean so that it can be modified with userchrome.css?  I don't know of any reason why it wouldn't be, but whoever works on the implementation could provide a more informed answer.
No, I mean if this style will be used across all platforms.
Depends on: 580235
No, it will be styled different on each platform, we'll cover the xp and classic variations in follow up bugs after we get Windows 7 implemented.
I've splitted bug 571784.
Depends on: 581858
i hope you will change the orange square button to a round button one. that will look nicer I think, and place it inline with the tabs of course. One more, consider adding saved password button , just like in Opera, so that we can manage our frequently used passwords better.
It isn't square, it has rounded corners. Furthermore, you can't just style the button anyhow you like it; there need to be consistency with caption buttons.
take Microsoft office 2007 products ribbon style (word,excel) I think that it will look like that, but slightly refined.
requesting to set this bug as blocking2.0:beta3
Meta bug can't be blocker.
Meta Bug can't be a blocker because it track actual bugs fixing problems in Firefox or giving Firefox new features hence it by itself can't fix problems or give Firefox features.
Depends on: 582632
>requesting to set this bug as blocking2.0:beta3

I need to sort through all of the dependent bugs and possibly file a few new ones if any are missing tomorrow. I'll also be requesting blocking on a lot of them as I go through them.
Depends on: 582664
Depends on: 583386
I've created the new bug 583386 to track all of the changes related to landing
an implemented version of iteration 5.  A lot of bugs are going to be duped
over to that bug.  I know standard bugzilla etiquette is that the older bug
doesn't get duped, but we need to reduce the number of different places that
these related changes are being discussed (also that single bug needs to block
beta 4).
Depends on: 580738
Depends on: 580740
No longer depends on: 576312
Attachment #448663 - Attachment is obsolete: true
No longer depends on: 578729
No longer depends on: 575271
Depends on: 584033
Depends on: 584955
Depends on: 585267
Depends on: 585304
Depends on: 586008
Depends on: 588710
Depends on: 589121
Depends on: 589126
Depends on: 589140
Depends on: 589146
Depends on: 589155
Depends on: 589254
Depends on: 589387
Depends on: 589435
Depends on: 589920
No longer depends on: 590146
Depends on: 590427
Depends on: 590736
Depends on: 590738
Depends on: 590740
Depends on: 590744
Two questions:

1. Will the titlebar be drawn at all times?  In previous landings it was only drawn when the menu-bar was hidden and the app-button shown.

2. Will the title be drawn in the new titlebar?  I haven't seen it in some of the previous builds.  Even if the default settings hide it, it would be nice to easily bring it back for users who want it.
(In reply to comment #54)
> Two questions:
> 
> 1. Will the titlebar be drawn at all times?  In previous landings it was only
> drawn when the menu-bar was hidden and the app-button shown.
> 
> 2. Will the title be drawn in the new titlebar?  I haven't seen it in some of
> the previous builds.  Even if the default settings hide it, it would be nice to
> easily bring it back for users who want it.

see bug 583905.
Depends on: 591005
Depends on: 592147
Depends on: 594264
Blocks: 595105
No longer blocks: 595105
Depends on: 595105
Depends on: 595106
Alias: FirefoxButton
Depends on: 595109
Depends on: 595330
Depends on: 592625
Depends on: 595540
Depends on: 583218
No longer depends on: 595106
Depends on: 596473
No longer depends on: 576093
Depends on: 597589
Depends on: 598293
No longer depends on: 589155
Depends on: 599779
Depends on: 604922
Depends on: 585370
Depends on: 608984
No longer depends on: 608984
Depends on: 612283
Depends on: 613859
Depends on: 615948
Depends on: 616384
Depends on: 610919
Depends on: 618008
Depends on: 618420
No longer depends on: 618420
Depends on: 628572
Can't find "View" submenu in Firefox button menu (the "View" menu contains useful and often used "Page Style", "Zoom", "Encoding" subitems, etc. when menu is enabled and Firefox button is disabled).

Hopefully this situation is temporary. It would be VERY unusable if there will no the "View" submenu in Firefox button menu (while browser layout with Firefox button enabled is very nice itself due to much more useful screen space use).

To wide extent, it should be possible that any of traditional main menu items could be displayed in Firefox button menu at least via settings if user wants this.

Firefox button should not be a usability regression. Currently, with useful submenus non-available, Firefox button IS a usability regression.

Thanks.
Have a look at Bug 592147 that is in the "depends on" list of this meta bug.
(In reply to comment #57)
> Have a look at Bug 592147 that is in the "depends on" list of this meta bug.

Thanks. But missing zoom controls is only small part of the much bigger problem—entire "View" submenu missing.
(In reply to comment #56)
> Can't find "View" submenu in Firefox button menu (the "View" menu contains
> useful and often used "Page Style", "Zoom", "Encoding" subitems, etc. when menu
> is enabled and Firefox button is disabled).

"Character Encoding" should be in the "Web Developer" menu, and "Page Style" had extremely low usage and is even being removed from the traditional menu -- see bug 611569.
(In reply to comment #56)
> Can't find "View" submenu in Firefox button menu (the "View" menu contains
> useful and often used "Page Style", "Zoom", "Encoding" subitems, etc. when menu
> is enabled and Firefox button is disabled).

Since bug 592147 is not likely to get fixed before FF4, zoom controls in View menu should somehow be copied to the Firefox menu.
No longer depends on: 588710
No longer depends on: 603793
Do you plan to make a better looking Firefox button for Linux?
Depends on: 719761
Depends on: 719763
Depends on: 708753
Depends on: 718875
Depends on: 783780
Depends on: 783782
Depends on: 638766
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.