I’m half-tempted to recategorize as a bug. The real trouble is each of those “buttons” is really a link, and the link targets are all
#. In a classic web page, that would just take you to the top of the page you’re already on, which is essentially the behavior described here. But Discourse’s scripting captures those clicks and renders drop-downs instead. That’s why you only see the problem when you try to open in a new window/tab.
A second problem is
# can really mess with front-end frameworks like Ember and Angular. A third is that it’s generally bad practice and I hate it and it should DIAF.
To my way of thinking, there are two possible solutions. Both of them start out the same way:
- Change the profile button to actually link to the profile page.
Then we have a choice:
Change the buttons to actually be
<button type="button" />. This is the preferred option from this idealistic, anal-retentive dev’s perspective.
If the buttons have to remain
<a/>, change the link targets to