How to use afterGetPageSource method of org.openqa.selenium.support.events.Interface WebDriverListener class

You are attempting to use x, the private HashMap, before it has been constructed. Hence you need to construct it first. You may do this by any of the following:

1) In the constructor:

x = new HashMap<Integer, String>(); 
// or diamond type  
x = new HashMap<>();

2) In the class as a field of this class:

private static HashMap<Integer, String> x = new HashMap<>();

3) In the initializer block:

static { 
    x = new HashMap<>();
}
// or the no-static block
{
    x = = new HashMap<>();
}

The problem you are having is a common one. All too often a new version of Firefox will not work with the latest version of Selenium Firefox WebDriver.

The solution is to use compatible versions of Firefox and Selenium Firefox WebDriver.

I recommend the following:

• Version 2.33.0 for Selenium Firefox WebDriver
• Version 18.0.2 for Firefox

This combination has always worked well for me.

You can also see which version of Selenium Firefox WebDriver is (theoretically) compatible with which versions of Firefox in the Release Notes.

Aditya,

As you said in your last comment that you are trying to access chrome of some other system so based on that you should keep your chrome driver in that system itself.

for example: if you are trying to access linux chrome from windows then you need to put your chrome driver in linux at some place and give permission as 777 and use below code at your windows system.

System.setProperty("webdriver.chrome.driver", "\\var\\www\\Jar\\chromedriver");
Capability= DesiredCapabilities.chrome();   Capability.setPlatform(org.openqa.selenium.Platform.ANY);
browser=new RemoteWebDriver(new URL(nodeURL),Capability);

This is working code of my system.

I know this is rather old, but you can get a simpler solution by using org.openqa.selenium.support.Color:

import org.openqa.selenium.support.Color;
String color = driver.findElement(By.xpath("//div[@class='gb_e gb_f gb_g gb_xb']/a")).getCssValue("color");
System.out.println(color);
String hex = Color.fromString(color).asHex();
System.out.println(hex);

It gives you a single line solution and even adds leading zeroes when required (something that the previous answers aren't accounting for)

Assuming that you use Java 8, you could do that using the Stream API with joining(CharSequence delimiter) as collector allowing to concatenate the input elements, separated by the specified delimiter, in encounter order as next:

String emails = emailAddresses.stream().collect(Collectors.joining(";"));

Try this:

 driver.manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);

Unpack it and place somewhere you can find it. In my example, I will assume you will place it to C:\Selenium\iexploredriver.exe

Then you have to set it up in the system. Here is the Java code pasted from my Selenium project:

File file = new File("C:/Selenium/iexploredriver.exe");
System.setProperty("webdriver.ie.driver", file.getAbsolutePath());
WebDriver driver = new InternetExplorerDriver();

Basically, you have to set this property before you initialize driver

Reference:

• Driver executable must be set by the webdriver.ie.driver system property

Well, I would guess that presenceOfElementLocated will be slighty faster because it's just check elements presence on the page while the visibilityOfElementLocated has to check the presence and whether is element visible.

But I think it really doesn't matter from the performance perspective (what's the point if you save 0.001 second during this checking?), you better choose appropriate method depending on your use case.

• use presenceOfElementLocated when you don't care whether if element visible or not, you just need to know if it's on the page
• use visibilityOfElementLocated when you need to find element which should be also visible

Look at the documentation for more info.

First of all lets be clear about what a WebElement is.

A WebElement is a reference to an element in the DOM.

A StaleElementException is thrown when the element you were interacting is destroyed and then recreated. Most complex web pages these days will move things about on the fly as the user interacts with it and this requires elements in the DOM to be destroyed and recreated.

When this happens the reference to the element in the DOM that you previously had becomes stale and you are no longer able to use this reference to interact with the element in the DOM. When this happens you will need to refresh your reference, or in real world terms find the element again.