innovark37 commented on issue #39965: URL: https://github.com/apache/superset/issues/39965#issuecomment-4541648867
@venkatamandavilli-code Thanks, that makes sense. My current thinking is that responsiveness and styling consistency would likely need to be handled by a dedicated print rendering mode rather than by reusing the normal interactive dashboard layout as-is. That mode could start with conservative rules: full-width vertical blocks, explicit print CSS, hidden interactive controls, preserved dashboard order, and visible chart error states. For large or data-heavy dashboards, I think the key distinction is whether the printable content can be safely rendered in one DOM pass. Dashboards without chunked visualizations may be printed in a single browser PDF call. Dashboards containing large table-like visualizations, server-side paginated data, or other content that should not be fully loaded into the DOM at once would likely need an internal incremental printing contract between the frontend and reporting worker. -- 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]
