<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: McAfee Anti-Phishing filter for Internet Explorer causes onclick events to not fire?</title>
	<atom:link href="http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/</link>
	<description>making the web work for you</description>
	<lastBuildDate>Thu, 23 Jul 2009 21:18:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sergio</title>
		<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/comment-page-1/#comment-25328</link>
		<dc:creator>Sergio</dc:creator>
		<pubDate>Wed, 10 Dec 2008 00:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.letsgomurphys.com/2008/03/21/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/#comment-25328</guid>
		<description>I have the same problem. Solution: Disable Mcafee Phishing Filter in browser complements!!!!</description>
		<content:encoded><![CDATA[<p>I have the same problem. Solution: Disable Mcafee Phishing Filter in browser complements!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/comment-page-1/#comment-21756</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 28 Sep 2008 00:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.letsgomurphys.com/2008/03/21/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/#comment-21756</guid>
		<description>@Nick,

Interesting. No, I don&#039;t have any documentation about the upcoming fix. I&#039;ll email you info for my contact at McAfee and maybe he can help you.</description>
		<content:encoded><![CDATA[<p>@Nick,</p>
<p>Interesting. No, I don&#8217;t have any documentation about the upcoming fix. I&#8217;ll email you info for my contact at McAfee and maybe he can help you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/comment-page-1/#comment-21473</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 15 Sep 2008 20:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.letsgomurphys.com/2008/03/21/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/#comment-21473</guid>
		<description>I have experienced a very similar problem recently on a web application for my company.  We have some form fields that have an onKeyPress event handler associated with them.  They are either formatting a dollar amount or a date, but in both cases they are monitoring the key press event and doing some formatting.  

The problem we&#039;re seeing is that numbers typed into these fields are being duplicated.  For instance, when a 2 is typed it appears as 22.  So far only three people have reported this problem. Two of them confirmed that disabling the McAfee anti-phishing filter stopped the double-digits.

Do you have a link to any documentation on the upcoming fix?</description>
		<content:encoded><![CDATA[<p>I have experienced a very similar problem recently on a web application for my company.  We have some form fields that have an onKeyPress event handler associated with them.  They are either formatting a dollar amount or a date, but in both cases they are monitoring the key press event and doing some formatting.  </p>
<p>The problem we&#8217;re seeing is that numbers typed into these fields are being duplicated.  For instance, when a 2 is typed it appears as 22.  So far only three people have reported this problem. Two of them confirmed that disabling the McAfee anti-phishing filter stopped the double-digits.</p>
<p>Do you have a link to any documentation on the upcoming fix?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/comment-page-1/#comment-18880</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 14 Jul 2008 19:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.letsgomurphys.com/2008/03/21/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/#comment-18880</guid>
		<description>Al,

Sorry for the delay. With so much spam, occassionally legit comments get overlooked.

I&#039;m glad to hear from you. I&#039;ve posted this issue in a handful of forums but haven&#039;t run into anybody experiencing the same problems. I haven&#039;t turned up anything at MSDN or the McAfee site either.

We were able to verify from one of our customers that new Dell laptops are shipping with McAfee by default. Yikes!

The good news is that I did report this finding to McAfee (with some examples of failing sites) and they do plan a patch to be released sometime during summer 2008. Until then he recommends the javascript:void(0) fix that we&#039;re using. Not sure how that will work with the problems you&#039;re describing.

Good luck!</description>
		<content:encoded><![CDATA[<p>Al,</p>
<p>Sorry for the delay. With so much spam, occassionally legit comments get overlooked.</p>
<p>I&#8217;m glad to hear from you. I&#8217;ve posted this issue in a handful of forums but haven&#8217;t run into anybody experiencing the same problems. I haven&#8217;t turned up anything at MSDN or the McAfee site either.</p>
<p>We were able to verify from one of our customers that new Dell laptops are shipping with McAfee by default. Yikes!</p>
<p>The good news is that I did report this finding to McAfee (with some examples of failing sites) and they do plan a patch to be released sometime during summer 2008. Until then he recommends the javascript:void(0) fix that we&#8217;re using. Not sure how that will work with the problems you&#8217;re describing.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Sparber</title>
		<link>http://www.letsgomurphys.com/usability/2008/03/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/comment-page-1/#comment-18069</link>
		<dc:creator>Al Sparber</dc:creator>
		<pubDate>Sat, 14 Jun 2008 05:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.letsgomurphys.com/2008/03/21/mcafee-anti-phishing-filter-for-internet-explorer-causes-onclick-events-to-not-fire/#comment-18069</guid>
		<description>Hi Michael,

It&#039;s not just links with explicit onclick events. Excrutiatingly correct DOM scripting techniques that programatically assign click events also fail in the same way with MacAfee phishing filter. Consider this link that fails:

&quot;&lt;a href=&quot;p7ssm_img_3/fullsize/ab112_fs.jpg&quot; rel=&quot;nofollow&quot;&gt;&lt;/a&gt;&quot;

A user with MacAfee will see the HREF executed, which in this case opens an image, even though a script is dynamically assigning an onclick. MacAfee is doing its deed at a much deeper level than you might think. THe above link is taken from an image slide show application that we market and a good number of folks are reporting failures - all being traced to MacAfee&#039;s filter. Here is the actual page:

http://www.projectseven.com/products/galleries/ssm/ssm_03.htm


What&#039;s scary is that it looks like Dell is installing this filter on its new computers.

If you here from MacAfee, please let us know. We will do the same.

-- 
Al Sparbner</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>It&#8217;s not just links with explicit onclick events. Excrutiatingly correct DOM scripting techniques that programatically assign click events also fail in the same way with MacAfee phishing filter. Consider this link that fails:</p>
<p>&#8220;<a href="p7ssm_img_3/fullsize/ab112_fs.jpg" rel="nofollow"></a>&#8221;</p>
<p>A user with MacAfee will see the HREF executed, which in this case opens an image, even though a script is dynamically assigning an onclick. MacAfee is doing its deed at a much deeper level than you might think. THe above link is taken from an image slide show application that we market and a good number of folks are reporting failures &#8211; all being traced to MacAfee&#8217;s filter. Here is the actual page:</p>
<p><a href="http://www.projectseven.com/products/galleries/ssm/ssm_03.htm" rel="nofollow">http://www.projectseven.com/products/galleries/ssm/ssm_03.htm</a></p>
<p>What&#8217;s scary is that it looks like Dell is installing this filter on its new computers.</p>
<p>If you here from MacAfee, please let us know. We will do the same.</p>
<p>&#8211;<br />
Al Sparbner</p>
]]></content:encoded>
	</item>
</channel>
</rss>

