PSA: splitting browser_protocol.pdl into multiple files in the Chromium codebase

[Alex Rudenko]

Hi CDP enthusiasts,

we are planning to split the browser_protocol.pdl into multiple pdl files by domain (tracking issue) to simplify editing of the file and organize ownership around specific CDP domains. The change might affect you if you are fetching the PDL file from the Chromium source tree directly. In that case, we suggest using the devtools-protocol package that will continue to contain the combined metadata in the JSON format.

Let me know if you have any concerns.

Best regards,
Alex

P.S. the group has been taken over by spam messages but we managed to clean it up and restore the functionality.

[Niranjan Rao]

From the end user perspective who just want to use connect using websocket, will there be any impact?

Regards,

Niranjan

On 8/12/25 00:00, 'Alex Rudenko' via chrome-debugging-protocol wrote:

Hi CDP enthusiasts, we are planning to split the browser_protocol. pdl into multiple pdl files by domain (tracking issue) to simplify editing of the file and organize ownership around specific CDP domains. The change might affect you if you are

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

 

ZjQcmQRYFpfptBannerEnd

--
You received this message because you are subscribed to the Google Groups "chrome-debugging-protocol" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-debugging-p...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/chrome-debugging-protocol/757bda50-418d-4a2e-877b-593de7dd57a7n%40googlegroups.com.

--
Niranjan Rao | Sr.Architect
he/his
Paymentus
Paymentus Corporation The Real-Time Bill Payment Company^TM

860 Hillview Court Suite 220 Milpitas CA 95035
www.paymentus.com

[Alex Rudenko]

Nope, no impact for end users! There could only be impact for library authors who used to fetch the pdl file to generate the client code.