Panos,
Glad to hear this will get resolved in the next release. I hope that the
Android "pan" issue (https://quality.livecode.com/show_bug.cgi?id=23245) and
others like it also get resolved. These are quite critical to everyday life on
mobile.
FYI... I found a work-around for the browserDocu
Hello again :)
Correction: We do have a patch for this issue, but it needs refined to make
sure the new behavior is 'correct'/'better' than the current behavior, so
it might not make it into 10.0.0 DP-2.
But it is in our TODO list for LC 10.
Kind regards,
Panos
--
On Wed, 16 Feb 2022 at 17:36,
Hello all,
Hopefully this will be fixed in the upcoming release of LC 10.0.0 DP-2
(https://quality.livecode.com/show_bug.cgi?id=21599)
Kind regards,
Panos
--
On Wed, 16 Feb 2022 at 12:04, hakan--- via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Maybe you could do a js callback on do
Maybe you could do a js callback on document loaded
window.onload = (event) =>
{
livecode.jscallback('The page has fully loaded’);
);
:-Håkan
> 15 feb. 2022 kl. 00:08 skrev Tom Glod via use-livecode
> :
>
> Hi Dan, I reported that bug a couple months back, it was confirmed and
> ac
Hi Dan, I reported that bug a couple months back, it was confirmed and
accepted, so its on the list to be fixed. I know there is work on the
browser being done, so one would assume.
You will find it will work sometimes, but mostly not.
I don't think there is much we can do, I would love to learn o
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
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
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
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
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".
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
Opps fix my post
I learned something today, wow, the target not only records mouse clicks,
but record what the message it going to
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and man
Had to add hack for mobile. This works
Local sHackDownloadCompleteFlag
on browserDocumentLoadComplete pURL
add 1 to sHackDownloadCompleteFlag
ntinfo ("download flag: " & sHackDownloadCompleteFlag)
if pURL is not empty then
dispatch "hideloader" to me
end if
show widget "Body
I learned something today, wow, the target only records mouse click budget
record what the message it going to
This was useful. It is still being call twice on mobile. NetWork tracer output.
I have to set a flag or same
ON desktop
info1/30/19 3:50:49 AM from loader: true
ope
> You could use "the target" do get the browser
> that is calling the handler...
.. and put the browserDocumentLoadComplete *only*
in the card's script (or the stack's script if the
widgets are on different cards).
___
use-livecode mailing list
use-liv
You could use "the target" do get the browser
that is calling the handler.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mail
16 matches
Mail list logo
