> Rick H. wrote:
> I am able to load the browser widget with a URL
> and go to the URL successfully.
>
> I can get the HTMLtext of the page I have browsed to just fine.
> What I have yet to do is to get the page source code of the page
> I have browsed to in LiveCode into a field.
The htmltext is
You can execute a small javascript to grab the HTML. I’ve done something
similar in an Instagram Scraper I just built….
First you need to set up a callback function in the widget under javascript
handlers e.g. jscallback then you can call a javascript that calls you back
with whatever you want.
Thanks for getting back to me on this.
> The htmltext is the page source code. So
>
> put the htmltext of widget "browser" into field 1
I thought it was the source code originally too,
but it doesn’t work correctly.
For example:
set the HTMLText of field "HTMLTextField1" to URL field "WebAddre
Htmltext of a field is not the same as htmltext of the browser widget. A
LiveCode field only supports a fraction of html. In your example you need to
just set the text of the field to see the page source. Setting htmetext forces
LiveCode to render the html and anything it does not understand
Try this:
put url tURL into tSource -- the source text
set the htmlText of fld "HTMLText" to tSource -- LC's display
LC only supports a subset of HTML, so when you put the source into a
field, only the supported parts go in. But you can grab the unadultered
source first.
On 4/17/19 1:22
Hi Brian and Jacqueline,
Thank you for your helpful responses.
put url tURL into tSource
..was exactly what I needed!
Thanks again,
Rick
> On Apr 17, 2019, at 2:57 PM, J. Landman Gay via use-livecode
> wrote:
>
> put url tURL into tSource -- the source text
__
On 4/15/19 3:17 PM, Richard Gaskin via use-livecode wrote:
It may be that the password isn't being set, or it may be a UI bug in
which the password is set but just isn't being displayed.
You can determine which is the case with a quick test build that does
something like:
answer line 10
Brian Milby wrote:
> Htmltext of a field is not the same as htmltext of the browser widget.
One of the best ideas Mark Waddingham ever had that he later abandoned
was about ten years ago when he proposed adding "xmlText" as a synonym
for "htmlText", flagging "htmlText" for eventual deprecation
J. Landman Gay wrote:
> Finally got to this. The password is saved in the standalone custom
> property set, but when testing on a trial standalone it isn't actually
> being used. So the answer is "no, you can't set a password on a mobile
> app via the standalone builder."
>
> After thinking about
