ndidomenico
asked on
Need to click twice on a link to get to the page in IE6
On a small web site that one of our assistant has created using FrontPage for our firm, we have noticed a "click" problem with our button links. Some clients (not all) using IE6 have to click twice on a link button to get directed to the link. Here is what happens exactly:
- when positionning the mouse over the button, the cursor will become a "hand" (instead of an arrow), and a highlight box will be drawn around the button, but the color of the button will not change as it should. Also, If you leave the mouse over the button for a few seconds, IE will display a little box saying "Click to activate and use this control".
- the first click will then change the color of the button, and the cursor will become an "arrow"
- the next click will then bring you to the proper page
We've tested this on clients using Netscape and Firefox and the links work as they should (so far): 1 click and you get the link. The buttons were created using Hover Buttons in FP.
Is this a IE configuration/security issue on the clients that has to be set ? Or is it something wrong the way we have created the Hover Buttons in FP ?
You can see the site with the problem at www.imk.ca.
Thanks
- when positionning the mouse over the button, the cursor will become a "hand" (instead of an arrow), and a highlight box will be drawn around the button, but the color of the button will not change as it should. Also, If you leave the mouse over the button for a few seconds, IE will display a little box saying "Click to activate and use this control".
- the first click will then change the color of the button, and the cursor will become an "arrow"
- the next click will then bring you to the proper page
We've tested this on clients using Netscape and Firefox and the links work as they should (so far): 1 click and you get the link. The buttons were created using Hover Buttons in FP.
Is this a IE configuration/security issue on the clients that has to be set ? Or is it something wrong the way we have created the Hover Buttons in FP ?
You can see the site with the problem at www.imk.ca.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the info war1.
I installed the patch (KB917425) mentionned in the link you sent me, and after rebooting, the links now work properly.
Now, I'm trying to understand the article, and what I should do:
If I read correctly the article in the Technet blog, they suggest strongly NOT to use this patch, because it is meant only to allow testing of some applications without the ActiveX Change, and that this ActiveX Change will be applied in the next cumulative IE security update. So if most of my IE visitors are eventually using the latest patches from MS, they will all experiment this "double-click" problem ???
Extract from Blog:
"... I STRONGLY advise that you NOT use this patch if you can avoid it, but if you do use the patch, as soon as you fix your application, remove the patch so that you can be sure that your applications work with the new ActiveX functionality..."
"...So when we release the next cumulative IE security update, customers will only be able to interact with Microsoft ActiveX controls loaded in certain web pages after manually activating their user interfaces by clicking on it or using the TAB key and ENTER key..."
Thanks.
I installed the patch (KB917425) mentionned in the link you sent me, and after rebooting, the links now work properly.
Now, I'm trying to understand the article, and what I should do:
If I read correctly the article in the Technet blog, they suggest strongly NOT to use this patch, because it is meant only to allow testing of some applications without the ActiveX Change, and that this ActiveX Change will be applied in the next cumulative IE security update. So if most of my IE visitors are eventually using the latest patches from MS, they will all experiment this "double-click" problem ???
Extract from Blog:
"... I STRONGLY advise that you NOT use this patch if you can avoid it, but if you do use the patch, as soon as you fix your application, remove the patch so that you can be sure that your applications work with the new ActiveX functionality..."
"...So when we release the next cumulative IE security update, customers will only be able to interact with Microsoft ActiveX controls loaded in certain web pages after manually activating their user interfaces by clicking on it or using the TAB key and ENTER key..."
Thanks.
ndidomenico,
Yes, next cumalative IE patch would result in ActiveX double click. So you need to modify your webpage to work with the new ActiveX functionality.
As a side note, Firefox users do not have this issue.
Yes, next cumalative IE patch would result in ActiveX double click. So you need to modify your webpage to work with the new ActiveX functionality.
As a side note, Firefox users do not have this issue.
ASKER
war1,
We also noticed that with Firefox and Netscape, we don't have this issue. Only in IE.
So I guess we'll have to create these buttons using something else than Hover Buttons in FrontPage if we don't want IE users to have this problem. I think I will launch a new question for this issue in the FrontPage section. I'm hoping there's maybe a way in FP to create/configure Hover Buttons so that it will not exhibit this behaviour when viewed in IE.
Thanks for the explanation and quick reply.
Thanks.
We also noticed that with Firefox and Netscape, we don't have this issue. Only in IE.
So I guess we'll have to create these buttons using something else than Hover Buttons in FrontPage if we don't want IE users to have this problem. I think I will launch a new question for this issue in the FrontPage section. I'm hoping there's maybe a way in FP to create/configure Hover Buttons so that it will not exhibit this behaviour when viewed in IE.
Thanks for the explanation and quick reply.
Thanks.
Glad to help, ndidomenico!
Here is more explanation why the ActiveX was changed.
http://blogs.technet.com/msrc/archive/2006/03/29/423560.aspx