There has been lots of controversy about the navigation bar, and today I suggest a solution I believe most people will agree to. The solution is simple: Add as many buttons to the navigation bar as the Scratch Team would like, hopefully including the Discuss button, and then add a new property to the navigation bar– make it slide. More specifically, a user can click and drag the navigation bar to make it slide/show different buttons. With this new feature in place, there would be no more button-related problems. This feature would be similar to the navigation bar (containing home, videos, shop, etc.) you can drag/slide on tablets.

Sorry if someone already suggested this feature.

Here are some reasons why you may want to support this suggestion, stated by @FancyFox:

FancyFoxy wrote:

Reasons I Support This:
1. I'm really tired of #Bring_it_back, and I feel like this is the best compromise I've seen yet. What makes me so tired? This.
2. Further step to support mobile device usage.
3. We can also get the “Contact Us”, “Community Guidelines” and “Wiki” button up there.

I assume a customizable navigation bar is a duplicate. Nonetheless, I do support that.

LionHeart70 wrote:

I assume a customizable navigation bar is a duplicate. Nonetheless, I do support that.

I haven't suggested a customizable navigation bar in the original post, but it is a good idea. What I have suggested is a navigation bar that you can scroll through/slide through.

Reasons I Support This:
1. I'm really tired of #Bring_it_back, and I feel like this is the best compromise I've seen yet. What makes me so tired? This.
2. Further step to support mobile device usage.
3. We can also get the “Contact Us”, “Community Guidelines” and “Wiki” button up there.

FancyFoxy wrote:

Reasons I Support This:
1. I'm really tired of #Bring_it_back, and I feel like this is the best compromise I've seen yet. What makes me so tired? This.
2. Further step to support mobile device usage.
3. We can also get the “Contact Us”, “Community Guidelines” and “Wiki” button up there.

Thank you for your support and for providing the reasons why you did support.

bump

I'm still doing #Bring_It_Back.

wait until I receive [bump v] :: events
do [bump v] :: operators

Charles12310 wrote:

I'm still doing #Bring_It_Back.

wait until I receive [bump v] :: events
do [bump v] :: operators

Okay, but I think this suggestion goes well with #Bring_It_Back.

FancyFoxy wrote:

Reasons I Support This:
1. I'm really tired of #Bring_it_back, and I feel like this is the best compromise I've seen yet. What makes me so tired? This.

Oooh yeah, that petition looks like it's going a little too far.

Support! V. Good idea.

PintOfMilk wrote:

Support! V. Good idea.

Thank you for your support.

I don't think this should be added, instead adding dropdowns from categories. For instance, Discuss, Explore, and the like could be under a Social drop down, where as Create and Tips could go under a Program dropdown. About and the Wiki would go under a ‘Info’ dropdown. That way, navigation would be sleek, compact, and easy in all languages.

braxbroscratcher wrote:

I don't think this should be added, instead adding dropdowns from categories. For instance, Discuss, Explore, and the like could be under a Social drop down, where as Create and Tips could go under a Program dropdown. About and the Wiki would go under a ‘Info’ dropdown. That way, navigation would be sleek, compact, and easy in all languages.

The method you're suggesting sounds good, but I still think my method is better.

First of all, I don't think there is really anything bad about my method, as nobody has stated anything bad about it, even the people who seemingly oppose this suggestion.

As I said, your method does sound good, but what if too many drop-down menus were added, and/or the names of the drop-down menus were too long in some languages? If either of these cases happen, then something like the removal of the discuss button on the navigation bar may happen.

Also, are the drop-down menus you are suggesting the type that will stay open once you click the button that opens the menu, or the type that will be open as long as you have your mouse hover over the menu? If its that latter type, then mobile users may experience difficulty in using the menu.

red_king_cyclops wrote:

braxbroscratcher wrote:

I don't think this should be added, instead adding dropdowns from categories. For instance, Discuss, Explore, and the like could be under a Social drop down, where as Create and Tips could go under a Program dropdown. About and the Wiki would go under a ‘Info’ dropdown. That way, navigation would be sleek, compact, and easy in all languages.

The method you're suggesting sounds good, but I still think my method is better.

First of all, I don't think there is really anything bad about my method, as nobody has stated anything bad about it, even the people who seemingly oppose this suggestion.

As I said, your method does sound good, but what if too many drop-down menus were added, and/or the names of the drop-down menus were too long in some languages? If either of these cases happen, then something like the removal of the discuss button on the navigation bar may happen.

Also, are the drop-down menus you are suggesting the type that will stay open once you click the button that opens the menu, or the type that will be open as long as you have your mouse hover over the menu? If its that latter type, then mobile users may experience difficulty in using the menu.

I understand that - I'd think it'd be the earlier, and if the current header, with five buttons, works, I'd imagine 1 button and 3 drop-downs would be fine.

braxbroscratcher wrote:

red_king_cyclops wrote:

braxbroscratcher wrote:

I don't think this should be added, instead adding dropdowns from categories. For instance, Discuss, Explore, and the like could be under a Social drop down, where as Create and Tips could go under a Program dropdown. About and the Wiki would go under a ‘Info’ dropdown. That way, navigation would be sleek, compact, and easy in all languages.

The method you're suggesting sounds good, but I still think my method is better.

First of all, I don't think there is really anything bad about my method, as nobody has stated anything bad about it, even the people who seemingly oppose this suggestion.

As I said, your method does sound good, but what if too many drop-down menus were added, and/or the names of the drop-down menus were too long in some languages? If either of these cases happen, then something like the removal of the discuss button on the navigation bar may happen.

Also, are the drop-down menus you are suggesting the type that will stay open once you click the button that opens the menu, or the type that will be open as long as you have your mouse hover over the menu? If its that latter type, then mobile users may experience difficulty in using the menu.

I understand that - I'd think it'd be the earlier, and if the current header, with five buttons, works, I'd imagine 1 button and 3 drop-downs would be fine.

That makes sense.

bump

braxbroscratcher wrote:

I don't think this should be added, instead adding dropdowns from categories. For instance, Discuss, Explore, and the like could be under a Social drop down, where as Create and Tips could go under a Program dropdown. About and the Wiki would go under a ‘Info’ dropdown. That way, navigation would be sleek, compact, and easy in all languages.

That's A Good Idea. I Like It Better Than The First One. The Community Guidelines Could Be Under Info.

bump

bump

(Again. And in a row.)

This is a good idea! It would make the navigation bar much more organized and compact, and allow for a bigger search bar. Support!