browserDocumentLoadComplete working correctly?

Klaus major-k klaus at
Wed Nov 20 15:24:07 EST 2019

Hi Tom

> Am 20.11.2019 um 19:43 schrieb Tom Glod via use-livecode <use-livecode at>:
> to me it seems like a nope.
> I would think that this is an issue with the browser widget not being able
> to detect when the page is completely "rendered" .... which is not the same
> as being completely "loaded".....
> as soon as I noticed that this message does not work consistently, I gave
> up on using it I did not further investigate the reasons for this.

OK, I see, maybe CURL, this is for a Mac app, can do this?

If yes, how to call CURL:
curl --url "url here..." 
will only return what "put url xxx into aVariable" does, show incomplete data.

Any hints very welcome!

> On Wed, Nov 20, 2019 at 12:50 PM Klaus major-k via use-livecode <
> use-livecode at> wrote:
>> Hi all,
>> no idea if this is a bug or feature:
>> When I use the message "browserDocumentLoadComplete"
>> this does not work correctly when dealing with "dynamically created pages"
>> (no idea if that is the correct term?).
>> -> put url "" into aVariable
>> does not work in these cases!
>> I set a custom property to the sourcecode of a browser object with some
>> tricks
>> that Hermann generously told me ->on browserDocumentLoadComplete
>> But when the message fires, the CP is EMPTY and I have to wait a little
>> longer until
>> the sourcecode is actually stored in that CP.
>> My question:
>> Is that correct behaviour of the "browserDocumentLoadComplete" message?



Klaus Major
klaus at

More information about the use-livecode mailing list