(In reply to Julian Descottes [:jdescottes] from comment #3)
1/ you can resize to very small dimensions or very big
dimensions, regardless of the limitations of the hardware/OS. The
implementation attached here will time out in such cases.
But this is ony in headless mode, right?
I believe we can support limitless resizing in headless mode because
all the painting code is mocked out, which means we’re not limited
by the hardware/OS. In normal windowed mode, I would think both
Chrome and we are limited by the surrounding system.
2/ different tabs can be resized independently. Which means among
other things that calling
browser.newPage on Firefox resets the
viewport for previous pages.
(In reply to Alexandre Poirot [:ochameau] from comment #4)
Oh that explain why juggler resize the <xul:browser> element:
I found it so weird to do that, but I did not realized it was actually similar to what happens in chrome.
I thought it was a workaround to not have to handle the size of chrome elements.
Would we be OK to do that?
I guess the primary mode of operation for Puppeteer is headless,
so the users wouldn’t necessarily notice the
beyond the visible application window. But how would we reconcile
this in windowed mode?