Re: debugging a CEF browser instance

2017-07-08 Thread Matthias Rebbe via use-livecode
Bernard, in case you are filing a bug report could you please post the bug id here? I would like to add a comment with some websites urls i have problems with when using the widget /CEF browser. Regards, Matthias Matthias Rebbe +49 5741 31 ‌matthiasrebbe.eu ‌ > A

Re: debugging a CEF browser instance

2017-07-08 Thread Mark Waddingham via use-livecode
Hi Bernard, There's no list, no. The widget is a reasonably thin wrapper around either CEF or (on Mac, iOS and Android) the system provided WebView. Without actually seeing cases to investigate which do not work as expected it is hard to advise what the problem might be (although 'cross origin

Re: debugging a CEF browser instance

2017-07-08 Thread Bernard Devlin via use-livecode
Hi Mark, I suspect this is the problem. Is there a list of things which the LC embedded browser forbids? Is there an explanation of the rationale for the embedded browser to behave differently from a default browser? This should be noted in the Dictionary, perhaps in the top entry of: com.livecod

Re: debugging a CEF browser instance

2017-07-07 Thread Mark Waddingham via use-livecode
Hi Bernard, On 2017-07-07 14:02, Bernard Devlin via use-livecode wrote: This makes it very clear that the problem relates to the way that LC is embedding the CEF browser. This is also confirmed by the fact the page will not load in LC browser widget on OS X. Is there any way of debugging the

Re: debugging a CEF browser instance

2017-07-07 Thread Bernard Devlin via use-livecode
Hi Mark, I've now found an app which has embedded the CEF browser within it. This embedded CEF browser has no trouble loading the page in question. This makes it very clear that the problem relates to the way that LC is embedding the CEF browser. This is also confirmed by the fact the page will

Re: debugging a CEF browser instance

2017-07-06 Thread hh via use-livecode
Hi all, a few remarks, may be marginal. Some of the problems with the CEF browsers arise from the fact that the "same origin policy" changed. Some of the latest versions of the main browsers make the access easier. Also, when using webGL, this differs between browsers and the browser widget in t

Re: debugging a CEF browser instance

2017-07-06 Thread Bernard Devlin via use-livecode
Hi Mark, I had no doubt that the debug log was disabled because enabling it by default would be expected to cause some significant slowdown. However, since this is a configurable option, I would have hoped that (at the very least) it could be turned on for situations such as the situation in which

Re: debugging a CEF browser instance

2017-07-06 Thread Jonathan Lynch via use-livecode
I am just using CEF on windows, in the browser widget. I have zero knowledge of Linux and so I am a bit hesitant to attempt that. My app leans heavily on the browser widget, so I guess Linux is not yet an option. Is Linux a big market for casual users? Anyway, I just think it would be nice to s

Re: debugging a CEF browser instance

2017-07-06 Thread Mark Waddingham via use-livecode
On 2017-07-06 08:39, Jonathan Lynch via use-livecode wrote: Why? In general there is a cost to logging - particularly CEF's which is very verbose. On Windows you might not notice (as stdout/stderr output is generally dumped to the equivalent of /dev/null), but on Linux if you happen to be wo

Re: debugging a CEF browser instance

2017-07-05 Thread Jonathan Lynch via use-livecode
Why? Sent from my iPhone > On Jul 6, 2017, at 1:45 AM, Bernard Devlin via use-livecode > wrote: > > Replying to myself, for anyone else who thinks it ought to be possible to > debug a browser widget. > > Ability to debug has been deliberately turned off. > https://github.com/livecode/livecode

Re: debugging a CEF browser instance

2017-07-05 Thread Bernard Devlin via use-livecode
Replying to myself, for anyone else who thinks it ought to be possible to debug a browser widget. Ability to debug has been deliberately turned off. https://github.com/livecode/livecode/commit/ccfab94499425b6245f98b3328ebd043876f9be7 ___ use-livecode mai

Re: debugging a CEF browser instance

2017-07-05 Thread Bernard Devlin via use-livecode
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 constr

Re: debugging a CEF browser instance

2017-07-05 Thread Jonathan Lynch via use-livecode
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 > On Jul 5, 2017, at 7:34 AM, Bernard Dev

Re: debugging a CEF browser instance

2017-07-05 Thread Bernard Devlin via use-livecode
I tried with 9.0 dp7. Still no luck. The webpage opens and works with both Chrome and Firefox. But not with the browser widget in either LC 8 or LC 9. I even tried with LC8.1.4 on OS X and it fails there too. I'm surprised no-one else has run into the need to access the debug log, browser consol

debugging a CEF browser instance

2017-07-04 Thread Bernard Devlin via use-livecode
After a very long time away from Livecode, I'm trying to get back into it. On 8.1.4 in the Windows IDE I have a browser instance where a standalone web page with some Javascript code is not working. The same page works if I load it into Chrome. So, I thought there might be a way to display the c