Does the latest Behat release contain the fix for 'JS 'change' not being fired when selecting an <option>'?

34 views
Skip to first unread message

mdnetto

unread,
Jul 13, 2012, 3:39:08 PM7/13/12
to be...@googlegroups.com
Hi there,

I've been running into this issue and was wondering if the fix for it is included in the latest version on Behat? I've had a look at the change log and can't see it.

Additionally, has anyone successfully upgraded to 2.4? Do you have any instructions on how to do it? I'm completely new to this.

Thanks,

Michelle

Oleksii Zozulenko

unread,
Jul 14, 2012, 1:35:19 AM7/14/12
to be...@googlegroups.com
I've extended Selenium2Driver from 2.3.5 behat/mink and copied latest changes from MinkSelenium2Driver for method selectOption. 
But Behat 2.4 still doesn't work for me and looks too ugly. 




---
Best regards, Oleksii Zozulenko

@clemherreman

unread,
Jul 14, 2012, 10:36:00 AM7/14/12
to be...@googlegroups.com
@Mdnetto :

The bug doesn't lie in behat itself, but in Mink drivers. The issue you're mentionning exist because the testcase are in the Mink repositories, whereas the bug fixes are in each driver repositories.

This bug is fixed in the Selenium2 driver (see https://github.com/Behat/MinkSelenium2Driver/pull/2). I can't tell for the other driver, but I'm almost sure that Selenium1 driver has this bug too.


@Oleksii Zozulenko: What doesn't work for you in behat 2.4, and why do you think it's ugly ?

The extension system is a huge move forward, especially for people integrating behat in other framework, like symfony2 or Yii


--
Clement Herreman
Lead developer at @widop, France
Reply all
Reply to author
Forward
0 new messages