Re: browserDocumentLoadComplete working correctly?

2019-11-21 Thread Klaus major-k via use-livecode
Hallo Hermann, > Am 21.11.2019 um 09:52 schrieb hh via use-livecode > : > > Klaus, > > looked in the scenario you mention. (I didn't say to use > messages of the browser widget ...) I did not say you did so, just rying out some things! :-) > This is your scenario (correct me if not): > > You

Re: browserDocumentLoadComplete working correctly?

2019-11-21 Thread hh via use-livecode
Klaus, looked in the scenario you mention. (I didn't say to use messages of the browser widget ...) This is your scenario (correct me if not): You have several pages on one or more foreign servers. These pages have dynamically generated content you wish to access and extract parts to custom prop

Re: browserDocumentLoadComplete working correctly?

2019-11-20 Thread Klaus major-k via use-livecode
Hi Hermann, > Am 20.11.2019 um 22:13 schrieb hh via use-livecode > : > > Yes, browserDocumentLoadComplete is working correctly and consistent > with HTML5, no bug here. > BrowserDocumentLoadComplete is fired as soon as the DOM is finished > incl. *reading* your script tags. ah, I see, thanks fo

Re: browserDocumentLoadComplete working correctly?

2019-11-20 Thread hh via use-livecode
Yes, browserDocumentLoadComplete is working correctly and consistent with HTML5, no bug here. BrowserDocumentLoadComplete is fired as soon as the DOM is finished incl. *reading* your script tags. *After* that your javascript is *executed*. The server and browser/ browser widget don't check/care wh

Re: browserDocumentLoadComplete working correctly?

2019-11-20 Thread Klaus major-k via use-livecode
Hi Tom > Am 20.11.2019 um 19:43 schrieb Tom Glod via use-livecode > : > > 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".

Re: browserDocumentLoadComplete working correctly?

2019-11-20 Thread Tom Glod via use-livecode
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 usin

browserDocumentLoadComplete working correctly?

2019-11-20 Thread Klaus major-k via use-livecode
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 "http://www.whatever.com/anything"; into aVariable does not work in these