Issue with Inconsistent Rendering of Superset Dashboard in Angular Application

[natwar585]

Bug description

I am currently working on embedding a chart from Apache Superset into an Angular application. The chart displays correctly within Superset itself, but when I try to display it in my Angular app, it does not render as expected.

Here are some details about the issue:

The chart shows up fine when accessed directly in Superset. but i try my angular app then Some charts and tables load fine, but others fail to render

I have attached images showing the Superset dashboard and the Angular app dashboard for reference. The issue is visible in the Angular app, where certain elements do not render

Screenshots/recordings

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hey there, @natwar585! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's squash those bugs together! 🤖

I found a similar closed issue regarding chart loading problems when embedding Superset charts in an HTML iframe, but no solution was found in the comments ^[1].

For your issue with inconsistent rendering in an Angular application, ensure that the EMBEDDABLE_CHARTS configuration is set to True in your Superset configuration. Additionally, configure CORS by setting ENABLE_CORS to True and specifying CORS_OPTIONS in your superset_config.py file. You may also need to adjust the content security policy (CSP) using flask-talisman to allow your domain to display Superset content ^[2][3].

If you encounter specific error messages, you might want to check for common exceptions like SupersetVizException, NoDataException, or SupersetSyntaxErrorException, which can provide more insight into the rendering issues ^[4].

Adjusting the logging settings to DEBUG mode can also help you gather more detailed information for debugging ^[2][5].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[rusackas]

It might be helpful to provide the errors that it links to (also available in the browser's JS console) though we'll probably have trouble supporting an Angular app we have no insight/access to.