$oIE.document.parentWindow.eval and execScript

[NewPlaza]

Hello,

I updated internet explorer to version 11 and find that my script no longer works. I have played around with it and found these two statements no longer run correctly.

Local $Count = $oIE.document.parentWindow.eval('Unit_Count')

$oIE.document.parentwindow.execScript('UpdateCount();')

I did find similar posts in the forums about IE10 and IE11 having issues but didn't find a solution.

I hope someone can assist on this matter.

Thanks.

 

[SmOke_N]

As far as execScript.  It's been deprecated by microsoft in IE11.

Just a note.  The last update for IE11 on Dec 18, broke alot of internal functions all across the coding communities.  The solution has been to uninstall the update until microsoft fixes it.

 

Try using these alternatives.

'?do=embed' frameborder='0' data-embedContent>>

[NewPlaza]

Thank you SmOke_N.

I will try your alternatives on Friday and let you know.

 

The solution has been to uninstall the update until microsoft fixes it.

 

So this move was not intentional by microsoft?

[SmOke_N]

So this move was not intentional by microsoft?

I don't work for them, nor do I know what their intentions may or may not be.  To date that I've read, I've not seen them admit the bug nor suggest there would be a fix for it soon.

[CliftonL]

Just call your function directly:

$myRet = $oIE.document.parentWindow.UpdateCount()

This is the way I do it and it doesn't seem to have any trouble. This way you don't need exeScript at all.

Edited December 25, 2014 by CliftonL

[NewPlaza]

Thanks CliftonL but this does not work. At lease in IE11 and me.

[NewPlaza]

SmOke_N,

Thanks for the sugestions but it seems they are not working either. For testing I tried the IEJSEvalExample.au3 and it simply opens a IE11 blank page then closes immediately. It displays no warnings or errors. There is no abandon IE processes left behind so at lease it closes IE gracefully.

The same test works great in IE8

Oh well,.. Thank you though.

Edited December 29, 2014 by NewPlaza

[bogQ]

Just call your function directly:

$myRet = $oIE.document.parentWindow.UpdateCount()

 

This is the way I do it and it doesn't seem to have any trouble. This way you don't need exeScript at all.

Thanks CliftonL but this does not work. At lease in IE11 and me.

strange, that should work if i remember correctly...

try it with '' maybe that is the problem in this case

 

$oIE.document.parentWindow.UpdateCount('')

Edited December 29, 2014 by bogQ

[SmOke_N]

@NewPlaza

Did you uninstall the update from Dec 18?

[NewPlaza]

SmOke_N,

No, I haven't.  I would but this move was the direction from our company. I do not want to circumvent a corporate change. I suppose if the pages them self were not woking then they may make an exception.

[NewPlaza]

oddly enough, I was able to update the count with the below statement.

$oIE.Navigate('JavaScript:UpdateCount();')

I'm 50% there! Ya!!

[SmOke_N]

I think there's a patch for it, and if your company wants everything to run, they'll change it.

IE11 update from Dec 18 has broke stuff across the internet, not just your script.

[MC256]

Derek Smith from Microsoft says they will be issuing a fix for the Dec 18 problem.  The fix should be released in the not-too-distant future -- "next IE cumulative update" [after 1/14/2015].

Here is a "bug tracker" entry for this problem:

https://connect.microsoft.com/IE/feedback/details/1062093/installation-of-kb3025390-breaks-out-of-process-javascript-execution-in-ie11

Search for "Derek" to read the MSFT announcement on this issue.

Edited February 3, 2015 by MC256