Hi, how do I do this? I tried installing v3 over the top of the beta, but init says that it's still using a local version?

Warning: jsreport-cli version mismatch:                                                                                                                                                                            
Global jsreport-cli is 3.0.0                                                                                                                                                                                       
Local jsreport-cli is 3.0.0-beta.2 

No problem, hope it helps someone else :)

@jan_blaha - Here you go :)

https://youtu.be/M_SNsqs1VR0

Actually, I've just realised you can pass launcher options to puppeter via the "launchOptions" config value!

e.g.

"extensions": {
    "chrome-pdf": {
       "launchOptions": {
           "defaultViewport" : {
             "width": 1920,
             "height": 10000
           }
       }
    },

This then changes the size of the image

hey @jan_blaha - I've actually managed to set this up (I'm pretty shocked I managed it, tbh!). I've got jsReports running on the VM in the datacenter, connected via a VPN and I'm able to step through the javascript on my desktop whilst chrome is being run by puppeteer. Its a reasonably straight forward setup, I'll make a video of the process to set it up if you think it would be of benefit to others?

Regards

Steve.

Hi @bjrmatos - something else I've read about when looking into this, it appears that puppeter defaults to a window size of 800x600, but you can override this via the defaultViewport option when launching puppeter

see: https://github.com/puppeteer/puppeteer/blob/v1.14.0/docs/api.md#puppeteerlaunchoptions

It would be great if there was a way you could expose those settings in a way that we can set them via the jsReport Studio UI.

I have a feeling this would fix the image issue plus the pdf scaling issue I opened tickets about. Using those options you can even remove the viewpoint completely or set it to 1920x10000 - i.e. sizes that make little sense for display on a monitor, but would allow you to get a screenshot of an entire page, for example.

Thanks, yeah I would normally, but I need to see the environment whilst its being run to see what javascript can see, if you know what I mean.

I've added that to the config, is there a way to log the command line that jsReport runs, so I can see if its having an effect?

Hi @bjrmatos - sure.

Please find it in my playground account, let me know if there's something I need to do to give you access.

btw, this is another related issue, perhaps you could look at it at the same time?

https://forum.jsreport.net/topic/2170/pass-custom-parameters-to-chrome-headless-how

The reason for the latter is because I need to find a way to detect when the page is rendering if its being rendered as HTML or to a PDF. If its HTML, I don't need to set the width of the highchart, if its a pdf, I do need to set the width. So being able to debug the chrome process remotely would be ideal to figuring out if there's a way to detect or infer that its being rendered in either format.

Thanks!

Steve.

Hi, I'm investigation ways to debug the headless chrome process whilst its generating the pdf and I notice you may be able to do it by using the --remote-debugging-port parameter you can pass to chrome.

I've tried to find the location where I could edit the source code to test this, but I can't find it.

What would I need to change to test this?

source: https://stackoverflow.com/questions/46017982/debugging-with-headless-browser

Hi, I've got a report that I'm using bootstrap to style it - I know about the printing issues and I've worked around them, the HTML output and PDF output is fine (I just need to scale the PDF output by 55% and it's fine - otherwise it appears the same as the image output.

I see there is a related topic from last year, has anyone got anywhere near solving this?
-> https://forum.jsreport.net/topic/1420/setting-browser-window-size-viewport-with-chrome-image-recipe

Image output:

pdf output:

html output: