Attached is a Selenium IDE testcase for this bug. Here is my log for this testcase:

• [info] Executing: |open | /maps | |
• [info] Executing: |click | link=Get Directions | |
• [error] Timed out after 30000ms
• [info] Executing: |type | d_d | Portland |
• [info] Executing: |type | d_daddr | Seattle |
• [info] Executing: |click | d_sub | |

As you can see, the testcase successfully executes, but throws a timeout error in the middle.

Selenium IDE 1.0.2
Firefox 3.0.11

This bug is reproducible on Selenium IDE 1.0.2/Firefox 3.5.2/OSX 10.5.6.

This really seems like a killer bug ... click is nearly useless depending on the underlying page structure – would love to have a workaround / patch ASAP!

Without a fix / workaround, we can't upgrade to FF 3.5 – as it disables the SIDE Extension after warning that it's not compatible.

Some add'l detail that might help:

• When the underlying page source contains an "onClick" to launch the content, the click works fine
• When the underlying page source contains an href that invokes javascript: (e.g. <a href="javascript: ...) the click works but reports a timeout

I've already managed to downgrade from FF 3.5/SIDE 1.0.2 back to FF 3.0.13 and SIDE 1.0b2 – so at least I'm working for the moment, but the upgrade does need to happen soon.

Happy to provide an "test site" if it helps!

+1 on Brent Rolland's comment... This bug is blocking our upgrade to the newest version of SIDE + Firefox.

Thanks, Brent, for tracking the bug down a little deeper. I hope it helps with a fix!

The same on FX 3.5/SIDE 1.0.2 on Linux.

I had to revert my FX and SIDE back to 3.0x and 1.0b2 too.

We are having the same problem using the SIDE 1.0.2b and FF 3.0.13.

just wanted to add that I'm experiencing the same problem with FF 3.0.13 + SIDE 1.0.2

very irritating bug. we use href="javascript:SpecifyCollapseMode(GeneratedWindowList,%201)" and as mentioned, the IDE clicks the link but waits for something unknown, then times-out (and indicates failure).

Please fix ASAP!

thank you!

Hey all - just letting you know I'm on the case for this. I really appreciate the simple test case that was provided!

works fine on my mac (leopard) but xp vm doesn't.

Here is a work around that I used to get around this issue. Use the setTimeout before the click action with a target value of something like 500, then setTimeout after the click action back to up 30000 or whatever you want.

I fixed my issue by putting a new line just before the click action:

IDE script: storeEval / javascript{"selenium.browserbot.findElement('link=Add').setAttribute('onclick',storedVars.func)"}

HTML source:
<tr>
<td>storeEval</td>
<td>javascript{"selenium.browserbot.findElement('link=Add').setAttribute('onclick',storedVars.func)"}</td>
<td>func</td>
</tr>
<tr>
<td>pause</td>
<td>1000</td>
<td></td>
</tr>
<tr>
<td>click</td>
<td>link=Add</td>
<td></td>
</tr>

when there are multiple "link=Add" on a page, it hits the first one. I wonder if I could use the xpath instead of the 'link=Add' in the middle of that storeEval to handle choosing from multiple link options

The above workaround - IDE script: storeEval / javascript{"selenium.browserbot.findElement('link=Add').setAttribute('onclick',storedVars.func)"}

also worked for me, in WinXP, FF 3.5.5, SIDE 1.0.2

as suggested xpaths do work although I had some fun with nested quotes as I couldn't seem to use \' within ' ' so used \" instead e.g.

javascript{"selenium.browserbot.findElement('//input[@name=\\"name[]\\"and @value=\\"some-value\\"]').setAttribute('onclick',storedVars.func)"}

Note selenium seems to escape my single escape to
"

just to let ppl know

since the bug is rather major for ppl having loads of side scripts to continue using (and the workaround really is a pain in the a** for ppl having lots of "click" commands)

well i kinda thought this bugs would be quickly fixed

about a year has passed now almost, firefox has evolved and now refuses to install the old selenium ide that was working. so i had to revert to an old firefox version that will soon no longer be supported by mozilla (if not already). so that means i'll have to install a virtual box to have a dedicated firefox install... it's getting complicated

so well, all in all, it might sound silly but : what do i need to do to fix this bug ?

Are people still having issues with this bug using the very latest Selenium IDE (3.0.6)?

Hello! I upgraded to the last version (Selenium IDE / March 26, 2010 / 1.0.6) and the issue was resolved.

We wrapped up the project and I no longer have a usable environment to try this ...

So, I won't complain if the bug gets closed – so long as others find it works now.

unfortunately our web testing VM had to be deleted so we no longer have a testing environment to double check that the latest version actually fixes this bug.
However, as far as i remember when i typed in my message last april i had tested it with the lastest SIDE version and observed that bug was NOT fixed, at least not for my scripts.

I do hope we'll have a testing environment soon to check this. Pls do not close the bug

good news so it seems (i hope i'm not speaking too quickly here...)

a maintenance windows has just opened for the project i had problems with regarding SIDE-316

i just installed Selenium IDE 1.0.11 on the old firefox 3.0.19 and it seems i can no longer reproduce bug SIDE-316 with the test scritps that used to reproduce it.

just to double check, i put back Selenium IDE 1.0.2 on the very same script using very same firefox
==> bug reappears again

i put back the least SIDE (1.0.11), run the same SIDE script and the bug has vanished again

i guess it means the bug has been fixed somehow

many thanks