PuppeteerCommunicator owns the websocket (or pipe) connection to the browser's DevTools endpoint, tracks frame/context/session IDs, queues CDP events, and matches asynchronous CDP responses back to the calls that requested them. browser.PuppeteerCommunicator exposes this connection on a live Browser instance using a Puppeteer-based engine (PuppeteerPort, PuppeteerPortHW, PuppeteerPipe, PuppeteerPipeHW). PuppeteerClient is built on top of PuppeteerCommunicator - every PuppeteerClient endpoint ultimately becomes one or more raw CDP commands sent through PuppeteerCommunicator and resolved against its response/event queues. Like PuppeteerClient, this is a completely custom CDP implementation written for GPAL - not derived from, or dependent on, the Node.js Puppeteer library or any third-party .NET Puppeteer package. WithPuppeteerCommunicator hands a client an existing communicator rather than letting it open its own.
Most workflows never touch PuppeteerCommunicator directly - PuppeteerClient and the Browser fluent API cover the vast majority of CDP operations. Reach for PuppeteerCommunicator only when you need a CDP domain/method that has no PuppeteerClient endpoint yet, or when building new PuppeteerClient endpoint mappings.
PuppeteerCommunicator is the transport layer. It speaks raw CDP, so use it to make the CDP calls GPAL has no fluent call for: the DevToolsMethods enum carries the complete set of CDP commands, so anything the protocol supports can be sent from here to supplement what GPAL already does.
//Every method is async and takes a session id last. Passing null uses the session the browser is on, which is what a workflow wants unless it is driving a specific tab, window or iframe it got the id for itself. GetAwaiter().GetResult() is how a synchronous GPAL workflow calls them; an async workflow awaits instead. SendCommand is the general case: the DevTools method, that method's parameters as an anonymous object, and the session. The parameter names are the CDP protocol's own, so width, height, deviceScaleFactor and mobile are what Emulation.setDeviceMetricsOverride documents, not names GPAL invented. It answers the raw CDP result, so read it the way the protocol describes it rather than expecting a GPAL shape. Calls differ in what they identify an element by. Some take a css selector, as GetCssAttributes does. Others take a backend node id, which is CDP's own handle for a node and is what a GPALElement carries, so those are for code that already has an element rather than for finding one.
// every call takes a session id last, and null means the session the browser is on now
IBrowser browser = GPAL
PuppeteerCommunicator cdp = browser
// 1
int nodeId = cdp
dynamic styles = cdp
dynamic answer = cdp
// 2
// the page to stop talking rather than for a fixed time
bool settled = cdp
// 3
// object of that method's own parameters, and the session
dynamic metrics = cdp
dynamic emulated = cdp
new { width = 1280, height = 800, deviceScaleFactor = 2, mobile = false }, null)
Showing off some plain text in these paragraphs eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quo veniam mollitia excepturi animi eum illum non libero sapiente provident assumenda, delectus voluptatum nobis sed dolorem adipisci laudantium incidunt. Error, ratione?
Here you can find different accents and emphasis sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
This is a link and how it could look like bestlinkinthebeautifulworld. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Here's just some classic bold text adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam notBoldSecondbestlinkinthebeautifulworld illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Obcaecati, iste distinctio veritatis eligendi laboriosam adipisicing elit illo nostrum corporis at adipisicing elit libero vel voluptas? Expedita, adipisicing facere dolores voluptatem ad ab rem assumenda soluta!
Other cuple of colors in case we want to emphasize several ways adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam adipisicing elit illo nostrum corporis at voluptatem libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta! Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quod veniam, quam ad expedita laborum sed at voluptates culpa ipsam ut vel. Ullam temporibus a mollitia quod aliquam ratione exercitationem nesciunt.
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta! Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quod veniam, quam ad expedita laborum sed at voluptates culpa ipsam ut vel. Ullam temporibus a mollitia quod aliquam ratione exercitationem nesciunt.
Lorem ipsum dolor sit amet consectetur adipisicing elit. Obcaecati, iste distinctio veritatis eligendi laboriosam illo nostrum corporis at libero vel voluptas? Expedita, facere dolores voluptatem ad ab rem assumenda soluta!
Lorem ipsum dolor sit amet consectetur adipisicing elit. Repudiandae quas consequuntur illo numquam assumenda autem exercitationem distinctio perspiciatis in natus. Eius dicta similique ipsam ipsa minima, nemo quae enim tempore.
GPAL
.CallIfNotFound(GenericCallIfNotFound)
.WithPublishToConsole();
//System.Drawing.Rectangle windowSize = new System.Drawing.Rectangle(10, 10, 1500, 1024);
// NOTE: we have to set browser = before we execute any steps
// this is due to the 'GenericCallIfNotFound' which might throw an exception, and BankScraper will not have the browser set when it calls scraper.Close()
// until the complete fluent line gets executed (meaning every step, meaning browser is not set until everything else succeeds)
browser = GPAL.Browser
.WithBrowserType(Enums.BrowserType.Chrome)
.WithProfileDataDirectory(ChromeProfileLocation)
.WithUseAutomationEngine(AutomationEngine.Selenium)
.WithWindowSize(new System.Drawing.Rectangle(0,0,1920,1080))
.ToGPALObject();