# Compatibility issues with MS Edge

**URL:** <https://talk.observablehq.com/t/compatibility-issues-with-ms-edge/2221>\
**Category:** Feedback\
**Created:** [July 30, 2019, 2:20pm UTC](https://talk.observablehq.com/t/compatibility-issues-with-ms-edge/2221 "2019-07-30T14:20:02Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [July 30, 2019, 2:20pm UTC](https://talk.observablehq.com/t/compatibility-issues-with-ms-edge/2221/1 "2019-07-30T14:20:02Z")

</div>

Hi folks.

I just dropped comments into a couple notebooks that I imagine you’ll see soon.

Related to one bug in particular: _It seems that the now built-in ‘download to SVG / PNG’ buttons in cells with charts won’t work on MS Edge_ (to whatever extent that bothers you). I discovered this first due to an error on the old-fashioned download buttons that you were using before implementing the options from the cell menu:

```auto
${DOM.download(await rasterize(chart), null, "Download as PNG")}
${DOM.download(await serialize(chart), null, "Download as SVG")}

```

The error given is:

```auto
TypeError: Object doesn't support property or method 'Symbol.iterator'

```

Hope this helps!

---

<div class="post-metadata">

**Author:** ![tom](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tom/32/2262_2.png) [@tom](https://talk.observablehq.com/u/tom)\
**Post date:** [August 6, 2019, 12:28am UTC](https://talk.observablehq.com/t/compatibility-issues-with-ms-edge/2221/2 "2019-08-06T00:28:11Z")

</div>

Hey Aaron,

Thanks for the report! We initially suspected that this was because Edge didn’t support NodeLists as iterators, but it looks like the problem goes deeper than that - it tracks back to [a lack of support for .toBlob](https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toBlob#Browser_compatibility) on Canvas elements and another failure with serializing SVG that we’re still tracking down. So this’ll be a little while until we track down a fix, or until Microsoft’s Chromium-based Edge successor launches. Sorry about that.