The meeting involved a problem-resolution discussion concerning a challenge faced with the "window print" feature within a WeWeb application. The specific issue was that the function was operating correctly in the adder, but not in the live application version. Upon clicking the print button in the live application, the print preview displayed all the elements with incorrect widths.
A series of potential troubleshooting and resolution strategies were proposed: 1. Diagnostic Techniques: It involves exploring the functionality in bits, for instance, running only the initial parts of the workflow and then launching the print window. 2. Utilising Media Queries: This method concerns adopting CSS for the print view, which could be more instantaneous compared to waiting for JavaScript to run. It involves using media queries specifying instructions for print and screen contexts. 3. Leveraging Delay: It involves increasing the time delay or eliminating the undo function after printing. 4. Creating a New Window for Print: It is a common approach of popping out and printing from a new window that's primed for printing. 5. Use of PDF Generation API: This approach involves designing a web page that's responsive and a flat PDF structure, which then gets transformed into a print-friendly format via a PDF generation API. 6. Using Window.open Method: This can help control the width of the page, which appears to be an issue in the current context. Lastly, Matthew was directed to post the challenge on the forum for additional support and to receive links helpful in problem resolution, like using media queries via the script tag. Throughout the meeting, it's evident there's a constant exploration of extricating this print setup from the usual responsive design properties of the webpage. The tools mentioned throughout the meeting were WeWeb, JavaScript, and CSS.
(Source: Office Hours 10/27/2023 )
