Jump to content
Sign in to follow this  
sdfg4545

IE, embedded, cant ID button: INNERTEXT not working?

Recommended Posts

sdfg4545

I cant seem to get to a button (Reset, Report) on a webpage .

object.InnerText returns '0'. What to use if not INNERTEXT

Working within IE, as an embedded object.

These are the buttons:

<input type="submit" name="TriageReport1:wfSearch" value="Report" id="TriageReport1_wfSearch" />

<input type="submit" name="TriageReport1:wfResetReport" value="Reset" id="TriageReport1_wfResetReport" />

----- I can get the embedded IE object

WinActivate ("iMedic Explore")

$hWnd = WinGetHandle("[CLASS:WindowsForms10.window.8.app.0.202c666]")

$oIE = _IEAttach ($hWnd, "embedded")

----- I can get the links on the page OK

$oLinks = _IELinkGetCollection ($oIE)

For $oLink In $oLinks

ConsoleWrite("link:" & $oLink.innerText & "Error : " & @error & " - Extended: " & @extended & @CRLF)

Next

----- I CAN get the buttons on the page, but no ID: INNERTEXT returns 0

$oInputs = _IETagNameGetCollection($oIE, "input", -1)

For $oInput In $oInputs

ConsoleWrite("submit 2: " & $oInput.InnerText & " Error : " & @error & " - Extended: " & @extended & @CRLF)

Next

Share this post


Link to post
Share on other sites
sdfg4545

Figured it out:

$oSubmit = _IEGetObjByName($oIE, "TriageReport1:wfSearch")

_IEAction ($oSubmit, "click")

Share this post


Link to post
Share on other sites
DaleHohm

Gook. Also

_IEPropertyGet with "innerhtml"

Dale


Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.