Hi all,

The zc.selenium package includes Selenium 0.7.1 (the latest release),
which includes this unresolved issue:


This impacts one of our projects, and the workaround described avoids
the problem.  It's not clear that the workaround is more than that (or
that it's not).  Is anyone else affected by this?  Does the workaround
have a negative impact for anyone?

I've attached a patch against zc.selenium that implements the
workaround.  I'd like to commit this in zc.selenium if there are no


Fred L. Drake, Jr.    <fdrake at gmail.com>
"Every sin is the result of a collaboration." --Lucius Annaeus Seneca
Index: resources/scripts/selenium-browserbot.js
--- resources/scripts/selenium-browserbot.js	(revision 70236)
+++ resources/scripts/selenium-browserbot.js	(working copy)
@@ -997,7 +997,9 @@
             triggerEvent(element, 'change', true);
+        /* See http://jira.openqa.org/browse/SRC-99
         triggerEvent(element, 'blur', false);
+        */
     catch (e) {
         // If the page is unloading, we may get a "Permission denied" or "Unspecified error".
Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to