Shivanigundlapalli commented on issue #37491:
URL: https://github.com/apache/superset/issues/37491#issuecomment-3818065597
Hi @maintainers,
Thanks for the detailed explanation and context.
I understand that the current PDF export flow relies on client-side DOM
capture
(dom-to-pdf / html2canvas), which does not support WebGL-based visualizations
like deck.gl charts. This explains why dashboards without deck.gl export
successfully, while dashboards containing deck.gl fail during PDF generation.
From what I see, there are two possible directions to improve this:
1. Improve or standardize the server-side (webdriver-based) rasterized PDF
export path so dashboards with deck.gl charts are exported reliably when
the
relevant feature flags are enabled.
2. Investigate whether a more robust client-side export approach (or a
graceful
fallback / user-facing warning) is feasible when deck.gl charts are
present.
I’d like to take this issue forward by first reproducing it locally and then
exploring which approach aligns best with Superset’s current roadmap and
architecture.
Before proceeding, could you please confirm:
- whether this issue is open for contribution, and
- if focusing on improving the server-side rasterized export path would be
the
preferred solution?
Happy to align with guidance before starting implementation.
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
