<div dir="ltr"><div><div><div>Isn't the be aware screen at about:config a notification ? <br></div>Why there and not for customizing the interface ? <br></div>That dose not make any sense, for anyone to know what about:config is he/she is either a power user or a normal user following a tutorial, no one will just randomly come up with the adress and start changing stuff. yet there is a warning there.<br>
</div>As for the interface I could very well see someone right clicking and messing everything up with one click.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 19, 2013 at 9:54 PM, Robert 'Bobby' Zenz <span dir="ltr"><<a href="mailto:Robert.Zenz@bonsaimind.org" target="_blank">Robert.Zenz@bonsaimind.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Mike.<br>
<br>
Thanks for opening this discussion, I'll try hard to be as constructive<br>
as positive, so if I strafe from that, please smack me back in shape or<br>
something. ;)<br>
And sorry if I'm asking questions you've already answered elsewhere,<br>
I've read through the thread and did not find answers to this.<br>
<br>
First of all, I'd like to show you how the top of my Firefox looks<br>
like, so that you understand why I reply: <a href="http://i.imgur.com/B6GUApz.png" target="_blank">http://i.imgur.com/B6GUApz.png</a><br>
<div class="im"><br>
> 1. We want to introduce more specific customization targets into<br>
> Firefox's UI. An example of a customization target would be a box<br>
> immediately to the right of the AwesomeBar, or one to the right of<br>
> the tabstrip, or one in our new menu panel. These boxes are places<br>
> where toolbar items can be dragged to and from.<br>
<br>
</div>Does that mean that you can only drag and change icons within certain<br>
areas of the toolbar?<br>
<div class="im"><br>
> 2. We want to remove (or deprecate) the add-ons bar<br>
<br>
</div>I have to thank you for that! No seriously, in some version you guys<br>
removed the addon bar from the default...and despite my first instinct<br>
that something changed, I *love* my additional screen estate now.<br>
<div class="im"><br>
> 3. We want to have an in-content customization palette to replace the<br>
> old window palette<br>
<br>
</div>So we'll be able to drag'n drop stuff like it was possible in the<br>
Gnome2/Mate panels? That's awesome.<br>
<div class="im"><br>
> 4. We're introducing a fixed Menu button at the end of the toolbar<br>
> which opens the "menu panel". The menu panel will contain one or more<br>
> customization targets.<br>
<br>
</div>If you're introducing a menu button, does that mean that the menubar<br>
will be removed (or not visible by default)? And if the menubar is<br>
visible, can I remove that button then?<br>
<div class="im"><br>
> 5. We're considering moving the back, forward, URL bar, refresh and<br>
> stop buttons to the start of the nav-bar, and making them immovable<br>
> when using the customization mode.<br>
<br>
</div>Given my layout, that's not great news for me. I moved everything into<br>
the menubar because I want to save screen real estate and *still* have<br>
the menubar readily available.<br>
You already said elsewhere that making that configurable (fixed/not<br>
fixed) is an additional maintenance cost which you're not sure if you<br>
want it or not. Of course I'd opt for it so that I still have a fully<br>
customizable menubar and toolbar.<br>
<br>
As I said before on Reddit, I think one of the biggest problems people<br>
have with these changes is that all they see is how Firefox starts to<br>
look and work like Chrome. I don't want to mitigate the work you're<br>
doing, but from the outside it seems like you're trying to copy Chrome,<br>
and the screenshots which are circulating from Australis seem to<br>
support that fear.<br>
We're all very happy and very glad that you people are driving the<br>
browser market and deliver a better browser with every version. But<br>
these changes seem to be driven by two ideas:<br>
1. To pursue that mystical "average user".<br>
2. To copy something successful, Chrome.<br>
Of course both are not going down well in the community. If the people<br>
would like to use a Chrome like browser, they'd use Chrome...but we're<br>
using Firefox because of the benefits.<br>
And for the first, I can only speak for myself, the last few times<br>
developers set off to chase that mystical average user, I ended up with<br>
hours and days of work to replace those applications. Seriously, there<br>
is no replacement for Firefox...not even close!<br>
<br>
May I suggest something, which will result in more work, though:<br>
Provide us with an option to unlock all locked items on the toolbar. I<br>
think that was stated before, but it would end all discussion around<br>
those changes. The benefit is that the "average user" can not break the<br>
experience, but everyone else can switch the flip and happily customize<br>
the toolbars and menubar to whatever they want.<br>
<div class="im"><br>
> Sorry for the long post,<br>
<br>
</div>Thanks for taking your time to write it and to read this.<br>
<span class="HOEnZb"><font color="#888888"><br>
Bobby<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
</div></div></blockquote></div><br></div>