Adjust the Layout of the Top Toolbar on the Issues Page

[kerwin612]

before:

after:

On the list page, labels and milestones do not serve as a switch-tab. Instead, they function as page navigation. The switch-tab is only appropriate for use on the labels and milestones pages, just like this:

[lunny]

What's the reason to change the labels and milestones's positions?

[kerwin612]

What's the reason to change the labels and milestones's positions?

As I described, on the default issue list page, labels and milestones do not fall under the functional definition of the switch-tab type. Instead, they serve as a page navigation function.
So, the first step is to change the current switch-tab into the buttons.
After switching to buttons, you will notice that with buttons both in front of and behind an input box, it will look uncoordinated. Therefore, I naturally moved it to the right side.
Coincidentally, after I made the modification, I compared it with GitHub and found that they also have the same layout (it's purely a coincidence).

[silverwind]

Imho, you want to modify template repo/issue/navbar so its consistent in all places. We shouldn't be singling out the repo issue page like that.

[kerwin612]

Imho, you want to modify template repo/issue/navbar so its consistent in all places. We shouldn't be singling out the repo issue page like that.

In fact, I have already explained it above. Let's just take a look through the page screenshots:

• /issues
  

• /labels
  
  

• /milestones
  
  

As I have repeatedly explained before, Page /issues should, of course, be different from Page /labels and Page /milestones. Therefore, it is impossible for it to share the same template(repo/issue/navbar) with Page /labels and Page /milestones.

[silverwind]

Hmm, if we could add a search bar to /labels, it could be made so all three pages use the same layout? Alternatively, add a SearchBar=boolean option to the subtemplate.

[kerwin612]

Hmm, if we could add a search bar to /labels, it could be made so all three pages use the same layout? Alternatively, add a SearchBar=boolean option to the subtemplate.

To be frank, my point of view is that these are two completely different sets of functional positioning. One is similar to a tab - like button, and the other is an ordinary button group. There's no need to abstract them into one template. It's a bit of over - abstraction.