# DOM select dropdown doesn't work in Chrome

**URL:** <https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715>\
**Category:** Feedback\
**Created:** [May 4, 2018, 6:16pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715 "2018-05-04T18:16:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aepton](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/aepton/32/559_2.png) [@aepton](https://talk.observablehq.com/u/aepton)\
**Post date:** [May 4, 2018, 6:16pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/1 "2018-05-04T18:16:11Z")

</div>

Seems to be a Chrome-specific bug. Neither the tagged template literal, nor DOM.select, work in Chrome (66.0.3359.117) at [https://beta.observablehq.com/@mbostock/standard-library](https://beta.observablehq.com/@mbostock/standard-library) but they both work fine in FF.

---

<div class="post-metadata">

**Author:** ![aaronkyle](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/aaronkyle/32/8106_2.png) [@aaronkyle](https://talk.observablehq.com/u/aaronkyle)\
**Post date:** [May 4, 2018, 6:20pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/2 "2018-05-04T18:20:25Z")

</div>

After exploring more closely, I can confirm that on Chrome (65.0.3325.181) with Windows 10 the dropdown created with `DOM.select(["one", "two", "three"])` isn’t functioning, nor is the tagged literal selection:

```
html`<select>
  <option>one</option>
  <option>two</option>
  <option>three</option>
</select>`

```

These elements appear, but the selection function isn’t working.

… I feel like this was working a few days ago.

---

<div class="post-metadata">

**Author:** ![aepton](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/aepton/32/559_2.png) [@aepton](https://talk.observablehq.com/u/aepton)\
**Post date:** [May 4, 2018, 6:31pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/3 "2018-05-04T18:31:16Z")

</div>

It’s quite odd - within a minute or two after posting, it was working in Chrome for me. Now it’s fine.

---

<div class="post-metadata">

**Author:** ![mbostock](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mbostock/32/9_2.png) [@mbostock](https://talk.observablehq.com/u/mbostock)\
**Post date:** [May 4, 2018, 6:32pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/4 "2018-05-04T18:32:42Z")

</div>

Do you have strict site isolation enabled?

> [@Slider doesn't seem to work in Chrome?](https://talk.observablehq.com/t/slider-doesnt-seem-to-work-in-chrome/195/2):
>
> Do you have [strict site isolation](https://www.chromium.org/Home/chromium-security/site-isolation) enabled in chrome://flags? We’ve heard reports of this causing exactly this issue. If you’re willing, try reseting your flags to their default values and see if that fixes the problem. Edit: Specifically, this known issue in Chrome: In some cases, clicking or scrolling on cross-site iframes may not work properly. For example, this can happen when there is a partly transparent overlay above an iframe. (This is fixed in Chrome 65.)

---

<div class="post-metadata">

**Author:** ![aaronkyle](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/aaronkyle/32/8106_2.png) [@aaronkyle](https://talk.observablehq.com/u/aaronkyle)\
**Post date:** [May 4, 2018, 6:44pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/5 "2018-05-04T18:44:16Z")

</div>

Oddly, for me, no: Strict site isolation on my machine is disabled. I have several dozen Observable tabs open at the moment (bad practice, I admit) as I a learn about ‘viewof’… to the extent this might affect things? I didn’t notice this to be an issue before (working primarily in Chrome), but interesting to be aware of the bug.

---

<div class="post-metadata">

**Author:** ![kelleyvanevert](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/kelleyvanevert/32/169_2.png) [@kelleyvanevert](https://talk.observablehq.com/u/kelleyvanevert)\
**Post date:** [May 4, 2018, 7:31pm UTC](https://talk.observablehq.com/t/dom-select-dropdown-doesnt-work-in-chrome/715/6 "2018-05-04T19:31:10Z")

</div>

I can confirm the behaviour, and in my case it wasn’t restricted to just the select but all kinds of input, and even (not) being able to inspect the iframe contents with Chrome’s devtools — and this all went away after disabling strict site isolation (input is possible as well as devtools inspection).