debugging a CEF browser instance

Bernard Devlin bdrunrev at
Wed Jul 5 14:55:36 CEST 2017

Thanks Jonathan for confirming that there is no debug mechanism for the
browser widget.

But what my examples shows is that one cannot rely on the browser widget to
present a working web page, even one that works in multiple standard
browsers (including Chrome).  This is not a web page of my construction,
but is one that is in use by other people.  So it's not that it's my
javascript that is failing, and therefore I can't carefully test each line
of javascript without taking their website apart and building it back up to
find the error.

LC needs to have some way of allowing at least the developer to see why a
page is not working within the widget.  The debuglog option of the CEF
browser widget shows
a) that the debuglog is being written to a system folder (and therefore
unlikely to be writeable)
b) that the browser widget has logging disabled anyway
c) that these options are hard-coded into the LC startup process

Anyone got suggestions about how this should be put forward as an
enhancement request/bug report?  It seems that a CEF executable ought to be
launchable with a supplied remote-debugging port. But that also does not
work with the libbrowser-cefprocess.exe which comes with Livecode.


On Wed, Jul 5, 2017 at 12:40 PM, Jonathan Lynch via use-livecode <
use-livecode at> wrote:

> Hi Bernard,
> I work with JS in the browser widget quite a bit.
> I have just gotten used to testing JS commands very carefully, step by
> step, because it does not really provide any debugging information.
> It would be nice to have that.
> Sent from my iPhone

More information about the use-livecode mailing list