Different result while using getEval on IE & FF

[Rohit]

Hi,

while executing the following line i get different result in FF i get
the correct result which is "null" however in IE i get the following
result "org.openqa.selenium.ie.InternetExplorerElement@31181a0" Can
somebody please explain why is this?

WebDriver driver = new FirefoxDriver();
/*WebDriver driver = new InternetExplorerDriver();*/
String baseUrl = "http://www.google.com";
final Selenium selenium = new WebDriverBackedSelenium(driver,
baseUrl);
selenium.open("");
System.out.println("\n Result is " + selenium.getEval
("window.document.getElementById(\"q\")"));

Cheers

Rohit

[Daniel Wagner-Hall]

Internet Explorer before version 8 has an interesting idea of what
getElementById should do, see
http://msdn.microsoft.com/en-us/library/ms536437(VS.85).aspx - it
actually returns the first element on the page with the name or ID of
the arugment, in a case-insensitive match. Is there a reason you
aren't using WebDriver or Selenium's locators?

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

[Rohit Maurya]

Hi,

we want to migrate from selenium to webdriver & currently in our framework we were using CSS however after moving to webdriver we r unable to use css as i believe it is not yet supported in webdriver.

Also in few places in the framework we have used JS to determine weather the element is present on the page or not. earlier selenium.getEval() used to return null if the element is not present however now after moving to Webdriver it is not returning null anymore.

Rohit

[Simon Stewart]

We're adding support for CSS locators: it's already there in the HEAD
version of the firefox driver (using the native Selectors API, so only
on recent Firefoxes), and we should be pushing it out to the other
drivers when we get a chance.

Can you please file an issue on the tracker for the difference in
behaviour between Firefox and IE for "getEval" --- I suspect we may
not be escaping the quotes properly.

Regards,

Simon

[Daniel Wagner-Hall]

I imagine this will be http://code.google.com/p/selenium/issues/detail?id=292 :)

[Rohit]

Hi Simon,

Sadly all our application are supported only on IE6 so i might have to
wait for some more time to start using CSS.
I am not very sure that this is caused due to escaping quotes because
when i was using single quotes i was getting another error, so the
issue no. 292
is logged for that.

I am raising a new issue for this. http://code.google.com/p/selenium/issues/detail?id=293

Rohit

On Dec 27, 5:08 pm, Daniel Wagner-Hall <dawag...@gmail.com> wrote:
> I imagine this will behttp://code.google.com/p/selenium/issues/detail?id=292:)

>
> On Sun, Dec 27, 2009 at 11:59 AM, Simon Stewart
>

> <simon.m.stew...@gmail.com> wrote:
> > We're adding support for CSS locators: it's already there in the HEAD
> > version of the firefox driver (using the native Selectors API, so only
> > on recent Firefoxes), and we should be pushing it out to the other
> > drivers when we get a chance.
>
> > Can you please file an issue on the tracker for the difference in
> > behaviour between Firefox and IE for "getEval" --- I suspect we may
> > not be escaping the quotes properly.
>
> > Regards,
>
> > Simon
>

> > On Fri, Dec 25, 2009 at 11:13 PM, Rohit Maurya <rohit.mau...@gmail.com> wrote:
> >> Hi,
> >> we want to migrate from selenium to webdriver & currently in our framework
> >> we were using CSS however after moving to webdriver we r unable to use css
> >> as i believe it is not yet supported in webdriver.
> >> Also in few places in the framework we have used JS to determine weather the
> >> element is present on the page or not. earlier selenium.getEval() used to
> >> return null if the element is not present however now after moving to
> >> Webdriver it is not returning null anymore.
> >> Rohit
>

> >> On Sat, Dec 26, 2009 at 3:39 AM, Daniel Wagner-Hall <dawag...@gmail.com>

> >> wrote:
>
> >>> Internet Explorer before version 8 has an interesting idea of what
> >>> getElementById should do, see

> >>>http://msdn.microsoft.com/en-us/library/ms536437(VS.85).aspx- it

> >>> actually returns the first element on the page with the name or ID of
> >>> the arugment, in a case-insensitive match.  Is there a reason you
> >>> aren't using WebDriver or Selenium's locators?
>

[Simon Stewart]

We plan on supporting CSS Selectors the same way we support XPath on
IE: by using a JS emulation. It won't be as fast as native CSS
Selectors, but it should work.

Simon