<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div>> * Remove the add-on bar from the core product
<br>
> <br>> This helps to cluster tools into the top portion of the browser by
<br>> default, and avoids incurring an entire toolbar when a user only has a
<br>> couple of addons installed
<br>
> <br>> The add-on bar could be re-inserted with another add-on.
<br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: arial,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div>I'd like to propose that the add-on bar is retained (perhaps re-dubbed as a footer bar) but instead wouldn't allow for add-ons auto-inserting buttons to it. As many users have stated in regards to this, it's very been incredibly useful for power users. I'd further add that the navigation bar lacks sufficient space in some cases while in reality such a bar would prevent the navigation bar becoming cluttered. Given that such a footer bar would be for power users, it's logical that the bar would need to be toggled on before it's shown in customisation view whereby users can add things to it manually.<br><br>Is there any data available regarding where users that have placed buttons manually have done so? I'd be very interested to see if the majority of users did opt for
the navigation bar or the add-on bar given that right now, all the way up to the Nightly builds, users have the option of either.<br><br>It's important to remember that the reason we advocate customisation in the manner we do is because we acknowledge that one size doesn't always fit-all. I don't believe it should require an add-on to add a bar to the bottom of the browser. Such an extra space would require little upkeep and given the plans for locking navigation actions to the navigation bar, it's not introducing any risk in regards to broken usability.<br></div></body></html>