Can't get past confirmation dialogs on FF4

[Robin Lee Powell]

I'm not sure if I'm having quite the same issue as
https://code.google.com/p/selenium/issues/detail?id=1457 ,but I think
so.

Using Perl and Test::WWW::Selenium (i.e. 1.0-style code) against
2.0b3, if a confirmation comes up in FF4 I have no way to get past it
except physically click "OK". It used to be handled automatically.

Does anyone know of any kind of workaround for this at all?

-Robin

[Robin Lee Powell]

Oh, also, does anyone know if using a 2.0 based language binding would
make it better? It seems unlikely, but...

-Robin

[Robin Lee Powell]

So, is no-one else having this issue, or is it that no-one knows how
to fix it?

I've seen it on different computers and versions of the server, so if
it's a configuration issue it's not a simple one.

-Robin

On Apr 7, 2:06 pm, Robin Lee Powell <rlpow...@digitalkingdom.org>
wrote:
> I'm not sure if I'm having quite the same issue ashttps://code.google.com/p/selenium/issues/detail?id=1457,but I think

[Robin Lee Powell]

OK, so, what do I do now?

I mean, a simple browser upgrade just made a huge pile of tests
useless. So what's the best next step, to not run into this sort of
thing again?

Do I want to try to debug the problem in FireFox 4? Do I want to try
Selenium 2.0 drivers? Something else?

-Robin

On Apr 14, 4:10 pm, Robin Lee Powell <rlpow...@digitalkingdom.org>

wrote:
> So, is no-one else having this issue, or is it that no-one knows how
> to fix it?
>
> I've seen it on different computers and versions of the server, so if
> it's a configuration issue it's not a simple one.
>
> -Robin
>
> On Apr 7, 2:06 pm, Robin Lee Powell <rlpow...@digitalkingdom.org>
> wrote:
>
>
>
>
>
>
>

> > I'm not sure if I'm having quite the same issue ashttps://code.google.com/p/selenium/issues/detail?id=1457,butI think

[Lutfi Dughman]

are you using webDriver?

in what mode are you using firefox.

is using IE in *iehta mode feasible?

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.

[Ross Patterson]

There's nothing simple about most browsers' major-version upgrades, least of all a Firefox release that has been in development for 5 years. But since you ask, I'd suggest a polite post to the selenium-developers list asking if there is anyone who can look at the issue you've cited and come up with a fix. One of the commenters seems to have provided a nice test case, so it should be easy to reproduce. And 2.0b3 was supposed to introduce Firefox 4 support, so I expect the developers would be interested in it.

Ross

[Mark Collin]

Just to clarify. 2.0b3 was released before FireFox 4. It provided FF4 beta
support but that is no guarantee that it will work in the final version.
Mozilla may have made lots of little changes between beta, RC and live.

Ross

-Robin

--

You received this message because you are subscribed to the Google Groups
"Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to
selenium-user...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-users?hl=en.

--
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

If you have received this email in error please notify postm...@ardescosolutions.com

[Robin Lee Powell]

On Apr 27, 9:13 pm, Lutfi Dughman <lutf...@gmail.com> wrote:
> are you using webDriver?

No; this is using http://search.cpan.org/dist/Test-WWW-Selenium/ ,
which is Selenium 1.0 based.

> in what mode are you using firefox.

I don't understand the question.

> is using IE in *iehta mode feasible?

For testing IE, yes. For testing FF4, not so much.

-Robin

[Robin Lee Powell]

On Apr 28, 5:53 am, Ross Patterson <rpatter...@parature.com> wrote:
> There's nothing simple about most browsers' major-version upgrades, least of all a Firefox release that has been in development for 5 years.

Fair enough; there was a bit of surprise/frustration at the total lack
of response thus far.

> But since you ask, I'd suggest a polite post to the selenium-developers list asking if there is anyone who can look at the issue you've cited and come up with a fix.  One of the commenters seems to have provided a nice test case, so it should be easy to reproduce.  And 2.0b3 was supposed to introduce Firefox 4 support, so I expect the developers would be interested in it.

Well, 2.0b3 was my big question: is this a problem because I'm running
Selenium-1.0/non-webdriver code? I mean, I was using the 2.0b3 server
but with Test::WWW::Selenium (Perl), which is 1.0-based.

After my last post I started playing with http://code.google.com/p/selenium/wiki/RubyBindings
in webdriver mode, and it doesn't seem to have the same problem, which
answers the question I had all along, which was "Am I supposed to be
moving to Selenium 2.0/webdriver at this point?".

-Robin

[Ross Patterson]

Yes, the problem may be because you're using the Selenium RC API. The WebDriver API gets more attention from the developers these days. The RC API only really seems to get changes when something breaks, and then it has to be important.

The RC API is still supported, and in fact is still what the vast majority of Selenium users are using. The WebDriver API still seems to be less stable than I would want it to be before *I* migrated to it. One of the biggest issues I'm concerned about is that there are lots of questions that get answered "that works in the <some language> bindings but not in the <other language> bindings" or "that works with <some browser> but not with <other browser>". For me, two of Selenium's key features have been that everything worked at an equal level of functionality in all the supported browsers (yes, XPath and JavaScript are slow in IE, but they still work), and that all of Selenium RC's functions worked the same in all of the supported languages (Perl and PHP are a bit different, their support seems to have grown up outside the Selenium developer group).

Ross

-----Original Message-----
From: seleniu...@googlegroups.com [mailto:seleniu...@googlegroups.com] On Behalf Of Robin Lee Powell
Sent: Thursday, April 28, 2011 8:57 PM
To: Selenium Users
Subject: [selenium-users] Re: Can't get past confirmation dialogs on FF4

[Robin Lee Powell]

Ugh.

That all really sounds like "you're screwed from both ends"; webdriver
gets all the dev time but has huge piles of problems. ;'(

Great information though, thank you very much.

-Robin

> After my last post I started playing withhttp://code.google.com/p/selenium/wiki/RubyBindings