I file a bug to extract a client interface for register protocol handler from
ChromeClient.
- Bug 90940 - Add ProtocolHandlerClient.h to the Modules/protocolhandler
(https://bugs.webkit.org/show_bug.cgi?id=90940)
In order to support this, the client needs to be supplementable first. I'm
This change looks reasonable for me.
I hope the client interface to be extracted from ChromeClient to its own.
ChromeClient is like a zoo of ifdefs, which modularization effort has
aimed to improve.
(I don't think we need to split the implementations of ChromeClient:
they can implement both
Hello folks,
I wonder whether protocol handler is able to be moved to the modules. I was
told that protocol handler belonges Current Non-Modules Using Module-Related
Techniques for Loose Coupling
== Current Non-Modules Using Module-Related Techniques for Loose Coupling ==
devicemotion
3 matches
Mail list logo