@ Mike… thanks… duh! (as he slaps himself on the side of the head) I was mixing up the props
the htmltext # with the url this is all static content so all that was needed was, assets /info web-loading.html <div class="container"> <img src="../img/global-icons/ajax_loader_big.gif" width="128" height="128" alt="ajax_loader_big"> </div> and then this command setWebURL put path_Assets() & "info/web-loading.html" into tLocalPath set the uirl of widget "body" to tLocalPath end setWebURL "of course" @ HH, thanks for the base64 method… I can use that in other instances. @ All, this really doesn’t get me what I want though, because as soon as we set the URL of the browser widget to the intended remote web page, our local page is of course "disconnected" the loader image is gone and the user is *still* staring at a blank screen waiting. I must have been working too late and didn't see either of these to things, which, are of course obvious. I'll start another thread on loading web pages/user notifications. On 1/6/18, 10:15 AM, "use-livecode on behalf of Mike Bonner via use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of use-livecode@lists.runrev.com> wrote: Then load the file as a url appearing like so.. "file:///path/to/your/html/file/myfile.html" At this point the browser widget has a path location so any relative addressing should work. _______________________________________________ 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/mailman/listinfo/use-livecode