# Screenshot node trouble?

**URL:** <https://talk.observablehq.com/t/screenshot-node-trouble/4842>\
**Category:** Feedback\
**Created:** [March 29, 2021, 12:29am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842 "2021-03-29T00:29:24Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sugi2000](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/sugi2000/32/246_2.png) [@sugi2000](https://talk.observablehq.com/u/sugi2000)\
**Post date:** [March 29, 2021, 12:29am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/1 "2021-03-29T00:29:24Z")

</div>

Recently, I can’t screenshot the SVG nodes on Observable with the browser’s developer tool.  
The images are on wrong coordination or broken layout.  
I tried on Firefox and Chrome.

Does anyone experience that?

---

<div class="post-metadata">

**Author:** ![jrus](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/jrus/32/586_2.png) [@jrus](https://talk.observablehq.com/u/jrus)\
**Post date:** [March 29, 2021, 2:06am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/2 "2021-03-29T02:06:59Z")

</div>

Can you link the notebook and attach an example screenshot?

---

<div class="post-metadata">

**Author:** ![tophtucker](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tophtucker/32/4781_2.png) [@tophtucker](https://talk.observablehq.com/u/tophtucker)\
**Post date:** [March 29, 2021, 2:40am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/3 "2021-03-29T02:40:59Z")

</div>

Hm yeah, like when I do “Capture node screenshot” on [@d3/force-directed-graph](https://next.observablehq.com/@d3/force-directed-graph), like this:

 ![Screenshot 2021-03-28 at 7.26.09 PM](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/6/6cd7fcf16f59eb391de8ea3dd78f52062730152e.jpeg)

…this is the resulting screenshot:

 ![next.observablehq.com_@d3_force-directed-graph](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/4/4695d8400c01fe72f789ee41a85393198877bf83.jpeg)

…which doesn’t just capture the SVG node in question. Is that what you mean? I haven’t known about that Chrome functionality for very long, so I don’t know if it used to work.

---

<div class="post-metadata">

**Author:** ![sugi2000](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/sugi2000/32/246_2.png) [@sugi2000](https://talk.observablehq.com/u/sugi2000)\
**Post date:** [March 29, 2021, 2:44am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/4 "2021-03-29T02:44:51Z")

</div>

Thank you. Yes, I got like that exactly.  
I often use the function even I know the image export function on Observable.  
It was functional last week, but I got this error today.  
So I guessed the cause isn’t the browsers…

---

<div class="post-metadata">

**Author:** ![tophtucker](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tophtucker/32/4781_2.png) [@tophtucker](https://talk.observablehq.com/u/tophtucker)\
**Post date:** [March 29, 2021, 3:02am UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/5 "2021-03-29T03:02:22Z")

</div>

I’ll look into it. It’s a great feature and more flexible than the cell-level “Download PNG”, so I’m sorry it’s broken!

---

<div class="post-metadata">

**Author:** ![mootari](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mootari/32/581_2.png) [@mootari](https://talk.observablehq.com/u/mootari)\
**Post date:** [April 15, 2021, 5:33pm UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/6 "2021-04-15T17:33:33Z")

</div>

@tophtucker That’s not really an error though. Triggering the screenshot hides the scrollbar, which in turn changes the notebook width. The `chart` cell references `width`, which is why taking a screenshot restarts the simulation.

---

<div class="post-metadata">

**Author:** ![tophtucker](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tophtucker/32/4781_2.png) [@tophtucker](https://talk.observablehq.com/u/tophtucker)\
**Post date:** [April 15, 2021, 5:50pm UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/7 "2021-04-15T17:50:13Z")

</div>

oh lol great point. though i think the more general problem is that it’s not cropped to the bounding box of the svg that i had selected in the chrome inspector. it cuts off the bottom right, and it shouldn’t include the markdown intro or metadata header at all

---

<div class="post-metadata">

**Author:** ![mootari](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mootari/32/581_2.png) [@mootari](https://talk.observablehq.com/u/mootari)\
**Post date:** [April 15, 2021, 6:25pm UTC](https://talk.observablehq.com/t/screenshot-node-trouble/4842/8 "2021-04-15T18:25:23Z")

</div>

> [@tophtucker](#):
>
> though i think the more general problem is that it’s not cropped to the bounding box of the svg that i had selected in the chrome inspector

Ah sorry, I missed that part. The “good” news is that it appears to be a Chrome bug:  
[https://bugs.chromium.org/p/chromium/issues/detail?id=1111398](https://bugs.chromium.org/p/chromium/issues/detail?id=1111398)

The bad (worse?) news is that Firefox doesn’t fare any better, but I haven’t found a bug report yet.

For the record, I also tried responsive mode / mobile preview in both browsers, and print preview in Chrome.

Edit: There may be more to this, because even capturing a node in the parent frame somehow causes the whole layout to rebuild:  
 ![](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/e/e19873de3e712c2c4774aae66dc72baba3e04d30.gif)
