title: HtmlUnitDriver does not appear to be loading page
body: <p>I'm trying to get HtmlUnitDriver to work in my development environment. As a beginner, I've tried implementing the example from the following page using the latest selenium server jar:
  <a href="http://code.google.com/p/selenium/wiki/GettingStarted" rel="nofollow noreferrer">http://code.google.com/p/selenium/wiki/GettingStarted</a></p>
  
  <p>Unfortunately, whenever I try to run this program, I get the following exception:</p>
  
  <pre><code>Exception in thread "main" org.openqa.selenium.NoSuchElementException: Unable to locate element with name: q
  For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
  Build info: version: '2.35.0', revision: 'c916b9d', time: '2013-08-12 15:42:01'
  System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_16'
  Driver info: driver.version: HtmlUnitDriver
      at org.openqa.selenium.htmlunit.HtmlUnitDriver.findElementByName(HtmlUnitDriver.java:853)
      at org.openqa.selenium.By$ByName.findElement(By.java:292)
      at org.openqa.selenium.htmlunit.HtmlUnitDriver$5.call(HtmlUnitDriver.java:1404)
      at org.openqa.selenium.htmlunit.HtmlUnitDriver$5.call(HtmlUnitDriver.java:1)
      at org.openqa.selenium.htmlunit.HtmlUnitDriver.implicitlyWaitFor(HtmlUnitDriver.java:1094)
      at org.openqa.selenium.htmlunit.HtmlUnitDriver.findElement(HtmlUnitDriver.java:1401)
      at org.openqa.selenium.htmlunit.HtmlUnitDriver.findElement(HtmlUnitDriver.java:419)
      at Justin.Main.main(Main.java:30)
  </code></pre>
  
  <p>I've tried modifying my code to incorporate the fixes implemented here:</p>
  
  <p><a href="https://stackoverflow.com/questions/15838526/htmlunitdriver-causes-problems-while-getting-an-url">HtmlUnitDriver causes problems while getting an url</a></p>
  
  <p>I've tried getting the URL of the page using <code>driver.getCurrentUrl()</code> after the call to <code>driver.get("http://www.google.com")</code>, but the string that is returned is <code>about:blank</code>. </p>
  
  <p>Similar code in this example would definitely work if I were to run it using FirefoxDriver, but to meet requirements, I need my script to run headless with selenium (it is okay if it is run with a specific BrowserVersion so long as it is headless).</p>
  
  <p>Any help would be greatly appreciated.</p>
  
  <p>UPDATE:</p>
  
  <p>This is the code I'm trying to run right now. I just want to see that I can get HtmlUnitDriver to work with something as simple as entering a search query into Google.</p>
  
  <pre><code>package Justin;
  
  
  import org.openqa.selenium.By;
  import org.openqa.selenium.WebDriver;
  import org.openqa.selenium.WebElement;
  import org.openqa.selenium.htmlunit.HtmlUnitDriver;
  
  
  public class Main {
  public static void main(final String[] args) {
      // Create a new instance of the html unit driver
      // Notice that the remainder of the code relies on the interface,
      // not the implementation.
      final WebDriver driver = new HtmlUnitDriver();
      ((HtmlUnitDriver)driver).setJavascriptEnabled(true);
  
      // And now use this to visit Google
      driver.get("http://www.google.com");
  
      try {
          Thread.sleep(30000);
      } catch (final InterruptedException e) {
          // TODO Auto-generated catch block
          e.printStackTrace();
      }
  
      // Find the text input element by its name
      final WebElement element = driver.findElement(By.name("q"));
  
      // Enter something to search for
      element.sendKeys("Cheese!");
  
      // Now submit the form. WebDriver will find the form for us from the element
      element.submit();
  
      // Check the title of the page
      System.out.println("Page title is: " + driver.getTitle());
  
  }
  }
  </code></pre>
  
  <p>UPDATE 2:</p>
  
  <p>This issue is very bizarre. I've tried the same code on my computer at home and it works perfectly fine with BrowserVersion set to Firefox or Internet Explorer. This issue is definitely being caused by the computer configuration at my workplace, although I still have no idea why this is happening.</p>