GitHub user dosubot[bot] added a comment to the discussion: Image is blank 
during pdf export in Superset UI

<!-- Answer -->
Good question! Node.js doesn't run in your browser—but it's used to **build** 
the JavaScript assets that run in your browser. Here's why it matters:

When Superset's frontend is compiled with an incompatible Node.js version (like 
Node 16 or 18 instead of the required 20.x), it can produce [missing or 
corrupted JavaScript bundles](https://github.com/apache/superset/issues/37282). 
These faulty assets then cause runtime issues in the browser, including 
[content disappearing on 
scroll](https://github.com/apache/superset/issues/38076#issuecomment-3922955086)—the
 exact symptom you're experiencing.

So the issue manifests in the Superset UI (browser), but the root cause is the 
build environment.

**That said**, if you're using the official Superset 6.0.0 Docker images or 
pre-built releases, they should already be compiled with the correct Node 
version. In that case, Node.js version wouldn't be your issue.

Since you've confirmed virtualization is disabled and the issue persists, let 
me ask:
- **Are you using official Docker images** or building from source?
- **Does the issue happen with all external image URLs**, or only specific 
domains?
- **Can you check your browser console** for any errors when the images go 
blank after scrolling?

This will help narrow down whether it's a build issue, an image loading issue, 
or something else in the rendering pipeline.


<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/500ab36e-9b0f-43a4-bd0f-639b399211cd?feedback_type=other)</sup>

[![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Good%20question%21%20Node.js%20doesn%27t%20run%20in%20your%20browser%E2%80%94but%20it%27s%20used%20to%20%2A%2Abuild%2A%2A%20the%20JavaScript%20assets%20that%20run%20in%20your%20browser.%20Here%27s%20why%20it%20matters%3A%0A%0AWhen%20Superset%27s%20frontend%20is%20compiled%20with%20an%20incompatible%20Node.js%20version%20%28like%20Node%2016%20or%2018%20instead%20of%20the%20required%2020.x%29%2C%20it%20can%20produce%20%5Bmissing%20or%20corrupted%20JavaScript%20bundles%5D%28https%3A//github.com/apache/superset/issues/37282%29.%20These%20faulty%20assets%20then%20cause%20runtime%20issues%20in%20the%20browser%2C%20including%20%5Bcontent%20disappearing%20on%20scroll%5D%28https%3A//github.com/apache/superset/issues/38076%23issuecomment-3922955086%29%E2%80%94t
 
he%20exact%20symptom%20you%27re%20experiencing.%0A%0ASo%20the%20issue%20manifests%20in%20the%20Superset%20UI%20%28browser%29%2C%20but%20the%20root%20cause%20is%20the%20build%20environment.%0A%0A%2A%2AThat%20said%2A%2A%2C%20if%20you%27re%20using%20the%20official%20Superset%206.0.0%20Docker%20images%20or%20pre-built%20releases%2C%20they%20should%20already%20be%20compiled%20with%20the%20correct%20Node%20version.%20In%20that%20case%2C%20Node.js%20version%20wouldn%27t%20be%20your%20issue.%0A%0ASince%20you%27ve%20confirmed%20virtualization%20is%20disabled%20and%20the%20issue%20persists%2C%20let%20me%20ask%3A%0A-%20%2A%2AAre%20you%20using%20official%20Docker%20images%2A%2A%20or%20building%20from%20source%3F%0A-%20%2A%2ADoes%20the%20issue%20happen%20with%20all%20external%20image%20URLs%2A%2A%2C%20or%20only%20specific%20domains%3F%0A-%20%2A%2ACan%20you%20check%20your%20browser%20console%2A%2A%20for%20any%20errors%20when%20the%20images%20go%20blank%20after%20scrolling%3F%0A%0AThis%20will%20he
 
lp%20narrow%20down%20whether%20it%27s%20a%20build%20issue%2C%20an%20image%20loading%20issue%2C%20or%20something%20else%20in%20the%20rendering%20pipeline.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/38244)

GitHub link: 
https://github.com/apache/superset/discussions/38244#discussioncomment-15921233

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to