Hi Steve,

First, glad to hear you've fared better with the app than Chris (smile).  I
believe the error will only occur if you have IE9 or later installed.  AIM
uses the IE engine to display html content including the conversation
history.  Apparently the way I was accessing the history was triggering one
of IE9's enhanced security procedures due to cross site scripting
vulnerabilities.  Basically it thought my app was a malicious script and so
it was blocking the app from functioning properly.  It still baffles me why
this was not an issue with IE8, since cross site scripting is really not a
new concept.  But despite my research and some messages to gw-scripting on
the subject, I never got a great explanation.  Thus, I had to change my
approach for reading the conversation history. 

So, if you have IE9 and the app has been working for you all this time then
count your blessings (smile).  But I'd be willing to bet that you haven't
had these problems because you're still running IE8.  Clear as mud?

-Cory

-----Original Message-----
From: Steve Jacobson [mailto:[email protected]] 
Sent: Saturday, September 24, 2011 1:21 PM
To: Cory Samaha; [email protected]
Subject: RE: Aim with Window-Eyes

Cory,

I've been using your app with AIM for some time and have not experienced
errors that I could attribute to your app.  
What did you fix?  Chris, what version of AIM are you running, so I know
what not to get?  <smile>

Best regards,

Steve Jacobson

On Sat, 24 Sep 2011 09:05:36 -0400, Cory Samaha wrote:

>FYI, I just submitted an update to the AIM app which fixes the below error.
>I really haven't had the time to devote as much attention to this app 
>as I would like, so Steve's comments are right on target.  If anyone 
>wants to take over the development or add to what I have done so far 
>feel free.  Just let me know if you want to modify what I have already
done.

>-Cory

>-----Original Message-----
>From: Stephen Clower [mailto:[email protected]]
>Sent: Saturday, September 03, 2011 10:42 AM
>To: chris hallsworth
>Cc: Portia Scott; gw-info
>Subject: Re: Aim with Window-Eyes

>Chris,

>If you feel this strongly about using AIM, and if no one else with 
>technical know-how is interested in scripting it further, then why not do
so yourself?
>That's what motivated me to begin work on the Miranda app for Window-Eyes.

>Regards,
>Steve



>On 9/3/2011 4:00 AM, chris hallsworth wrote:
>> I have reported my concerns to AIM and all I have gotten back is use 
>> Miranda. Sorry to rant guys but what if Miranda is not the person's 
>> choice of client? I feel we should have a choice in what we use like 
>> the sighted do. Also what is the point of doing scripts for AIM when 
>> the client doesn't seem to work properly in the first place. I use 
>> AIM with the free screen reader and it works great. I just think 
>> while Miranda is a great client it will not suit everybody. I liked 
>> it but would rather prefer a client where I can just get up and going 
>> quickly. Not so with Miranda. You not only have to get a third party 
>> add-on; you also need to configure Miranda so it behaves kind of like 
>> a standard Windows application if you know what I mean. By all means 
>> if you are happy with Miranda, great. But I just think we should have 
>> a choice in what we can use. Rant over.
>>
>>
>> Chris Hallsworth
>> Sent from Thunderbird
>>
>> On 03/09/2011 04:21, Portia Scott wrote:
>>> Hey all,
>>>
>>> I installed the Window-Eyes scripts for Aim, and I get a weird erro. 
>>> It says:
>>>
>>> aim.js - Microsoft JScript runtime errorLine 307 Column 
>>> 3'frames.0.document' is null or not an object<  0x800A138F
>>>
>>> Anyone have this issue with the Aim scripts?
>>>
>>> Portia.If you reply to this message it will be delivered to the 
>>> original sender only. If your reply would benefit others on the list 
>>> and your message is related to GW Micro, then please consider 
>>> sending your message to [email protected] so the entire list will
receive it.
>>>
>>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You 
>>> can manage your list subscription at http://www.gwmicro.com/listserv.
>>>
>>>
>> If you reply to this message it will be delivered to the original 
>> sender only. If your reply would benefit others on the list and your 
>> message is related to GW Micro, then please consider sending your 
>> message to [email protected] so the entire list will receive it.
>>
>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You 
>> can manage your list subscription at http://www.gwmicro.com/listserv.

>--
>--
>Stephen Clower
>Product support specialist
>GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
>260-489-3671 * gwmicro.com
>If you reply to this message it will be delivered to the original 
>sender only. If your reply would benefit others on the list and your 
>message is related to GW Micro, then please consider sending your 
>message to [email protected] so the entire list will receive it.

>GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can 
>manage your list subscription at http://www.gwmicro.com/listserv.

>If you reply to this message it will be delivered to the original 
>sender only. If your reply would benefit others on the list
and your message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.

>GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can 
>manage your list subscription at
http://www.gwmicro.com/listserv.





If you reply to this message it will be delivered to the original sender only. 
If your reply would benefit others on the list and your message is related to 
GW Micro, then please consider sending your message to [email protected] so 
the entire list will receive it.

GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage 
your list subscription at http://www.gwmicro.com/listserv.

Reply via email to