# Cannot middle-click or control-click on embedded topics to open in new tab

**URL:** https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711
**Category:** Bug
**Created:** [January 11, 2018, 12:09am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711 "2018-01-11T00:09:12Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![barryvan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barryvan/32/82635_2.png) [@barryvan](https://meta.discourse.org/u/barryvan)
#### Post date: [January 11, 2018, 12:09am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/1 "2018-01-11T00:09:12Z")

</div>

This is happening to me in Firefox.

If you middle-click or control-click on the title of a topic embedded in another, it doesn’t open in a new tab – instead, it replaces the current tab. It also seems to do a full load, rather than the normal AJAXy Discourse load.

In this video, I’ve middle-clicked; control-clicking behaves the same way.

[https://global.discourse-cdn.com/meta/original/3X/7/6/76ca3b08b9ff908edb357c09e3a6009d1ee910bd.mp4](https://global.discourse-cdn.com/meta/original/3X/7/6/76ca3b08b9ff908edb357c09e3a6009d1ee910bd.mp4)

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [January 11, 2018, 1:03am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/2 "2018-01-11T01:03:28Z")

</div>

Oh wow, does the same thing in Chromium. That seems… suboptimal.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 11, 2018, 1:05am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/3 "2018-01-11T01:05:47Z")

</div>

This is usually easy to fix with markup, @techapj can you have a look?

---

<div class="post-metadata">

### Author: ![Mahya](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mahya/32/87407_2.png) [@Mahya](https://meta.discourse.org/u/Mahya)
#### Post date: [January 15, 2018, 7:54am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/4 "2018-01-15T07:54:38Z")

</div>

I also have this problem.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [January 15, 2018, 10:56pm UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/5 "2018-01-15T22:56:53Z")

</div>

Yes, everyone has this problem.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [January 24, 2018, 3:29pm UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/7 "2018-01-24T15:29:44Z")

</div>

Also doesn’t work for oneboxed links ⬇

> [@Better detection of "cookies deleted" in the application](https://meta.discourse.org/t/better-detection-of-cookies-deleted-in-the-application/78800):
>
> Occasionally users may delete all cookies or in self hosted situations (which do not have auth token set via env) junk redis. When this happens behaviour is kind of odd. It looks like you are logged in: If you are browsing a secure topic, you only see placeholders: Depending on the site you are on (requires login or not) you will start seeing lots of 302s or 403s Instead: If we detect a user is somehow no longer logged in, we should open a modal saying “looks like you w…

---

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [January 24, 2018, 4:08pm UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/8 "2018-01-24T16:08:49Z")

</div>

Yes, this is happening for all _internal_ oneboxed links which expands on click. Spent some time on it today, but can’t figure out a simple markup fix. This might be linked to our click tracking code. Will dig more into it.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 25, 2018, 12:35am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/9 "2018-01-25T00:35:58Z")

</div>

I can middle click just fine on that, the area I’ve outlined in the pink box, and it opens in a new tab for me:

 ![image](https://global.discourse-cdn.com/meta/original/3X/6/9/69224e7dcd62c890dc7fa5f9d68d24cccfc43892.png)

So… how is this a bug, again? Only on certain browsers?

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [January 25, 2018, 1:07am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/10 "2018-01-25T01:07:48Z")

</div>

Must be a browser thing, because middle-clicking on the link you pink-boxed in zogstrip’s most recent post gives the behaviour originally described: doesn’t open a new tab, but instead loads the clicked link in the same tab. Just to be sure, I tried in an anon incognito window with all plugins disabled, still broken. I’m using Chromium 63.0.3239.84 on Linux, and I also I tried it in Firefox 52.5.2 (again on Linux) and it did the same thing.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 25, 2018, 1:19am UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/11 "2018-01-25T01:19:38Z")

</div>

In Windows I can’t repro in Chrome, but I can in Firefox.

**Right clicking and selecting “open in new tab” works in Firefox** , though. Maybe do that, since there is an easy workaround? I don’t want @techapj to burn tons of time on this.

---

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [January 25, 2018, 4:39pm UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/12 "2018-01-25T16:39:26Z")

</div>

Fixed via:

[https://github.com/discourse/discourse/commit/8b59ce9183273b43f119b2cf95f4f41dca296bf0](https://github.com/discourse/discourse/commit/8b59ce9183273b43f119b2cf95f4f41dca296bf0)

This was happening for all anonymous users (or logged in users with “Open all external links in a new tab” disabled) on all browsers. Hence the repro was inconsistent.

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [January 26, 2018, 11:00pm UTC](https://meta.discourse.org/t/cannot-middle-click-or-control-click-on-embedded-topics-to-open-in-new-tab/77711/13 "2018-01-26T23:00:01Z")

</div>

This topic was automatically closed after 29 hours. New replies are no longer allowed.
