# Quote reply not working in IE 11

**URL:** https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595
**Category:** Bug
**Created:** [5월 12, 2017, 3:02오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595 "2017-05-12T15:02:24Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![blake](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blake/32/157322_2.png) [@blake](https://meta.discourse.org/u/blake)
#### Post date: [5월 12, 2017, 3:02오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/1 "2017-05-12T15:02:24Z")

</div>

When using IE 11 highlighting text does not reveal the “quote” pop up. It works fine in chrome and I confirmed myself that this doesn’t work in IE 11. Apparently we [support](https://meta.discourse.org/t/discourse-will-be-dropping-ie9-support-in-2016/31090) back to IE 10.

When you highlight text these errors show up in the console:

 ![](https://global.discourse-cdn.com/meta/original/3X/8/2/8267894a8ae9112fb91d76bf3b53f473ff8e9059.png)

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [5월 12, 2017, 3:10오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/2 "2017-05-12T15:10:22Z")

</div>

Related to  
[https://github.com/discourse/discourse/commit/ce9fe213fdfd0a90bc8ed0e67b518bf34fd18762](https://github.com/discourse/discourse/commit/ce9fe213fdfd0a90bc8ed0e67b518bf34fd18762)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 12, 2017, 3:44오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/5 "2017-05-12T15:44:23Z")

</div>

This is quite bad, @eviltrout can you fix this, seems pretty straight forward to use jQuery closest here as opposed to DOM closest

---

<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: [5월 12, 2017, 3:46오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/7 "2017-05-12T15:46:25Z")

</div>

I think this should fix it

```plaintext
const withinCooked = $(range.startContainer.parentNode).closest('.cooked');

```

Haven’t tested though.

---

<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: [5월 12, 2017, 5:40오후 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/8 "2017-05-12T17:40:25Z")

</div>

Even edge does not support native Closest until very latest version so this should be avoided.

> **[Can I use... Support tables for HTML5, CSS3, etc](https://caniuse.com/#feat=element-closest)**
>
> "Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.

Per [the wikipedia Edge release history](https://en.wikipedia.org/wiki/Microsoft_Edge#Release_history) it looks like “Edge 15” is only released as of April 11, 2017.

---

<div class="post-metadata">

### Author: ![smulder](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/smulder/32/72115_2.png) [@smulder](https://meta.discourse.org/u/smulder)
#### Post date: [5월 13, 2017, 3:17오전 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/9 "2017-05-13T03:17:17Z")

</div>

Not working with my obscure webkit browser either.

```
ii libjavascriptcoregtk-1.0-0:i386 2.4.11-3 i386       
ii libwebkitgtk-1.0-0:i386 2.4.11-3 i386
hi surf 0.6-1 i386
```

When I highlight text, the browser spits out this console error:

` ** Message: console message: https://global.discourse-cdn.com/meta/assets/application-09c15314fa7c40b3b300d2faf6824148ef6d3356ac149ccde164b442a25aa9c3.js @20: TypeError: undefined is not a function (evaluating ‘r.startContainer.parentNode.closest(“.cooked”)’)`

`
(Thanks everybody.)`

---

<div class="post-metadata">

### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [5월 15, 2017, 12:28오전 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/10 "2017-05-15T00:28:15Z")

</div>

Fixed in

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

I’ll need to test it out on IE11 once it gets deployed.

---

<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: [5월 16, 2017, 1:00오전 UTC](https://meta.discourse.org/t/quote-reply-not-working-in-ie-11/62595/11 "2017-05-16T01:00:15Z")

</div>

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