Appears as if any execution of JavascriptExecutor is causing this error to occur.  Verified
on Firefox 35; does not occur on Chromedriver or IEDriverServer.  Reverted back to
FF 34 as a workaround.

I'm seeing the same issue since upgrading to Firefox 35
Selenium version: 2.44.0 c~ bindings
OS: Window 7
Browser: Firefox
Browser version: 35

Sample code:
using OpenQA.Selenium;
using OpenQA.Selenium.Firefox;

namespace SeleniumSandbox2
{
    class Program
    {
        static void Main(string[] args)
        {
            var driver = new FirefoxDriver();
            driver.Navigate().GoToUrl("http://www.google.co.uk");
            ((IJavaScriptExecutor)driver).ExecuteScript("arguments[0].scrollIntoView(true);",
driver.FindElement(By.CssSelector("#gb_70")));
       }
    }
}

System.InvalidOperationException was unhandled
  HResult=-2146233079
  Message=arguments[0] is undefined (UnexpectedJavaScriptError)
  Source=WebDriver
  StackTrace:
       at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
       at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute,
Dictionary`2 parameters)
       at OpenQA.Selenium.Remote.RemoteWebDriver.ExecuteScriptCommand(String script,
String commandName, Object[] args)
       at OpenQA.Selenium.Remote.RemoteWebDriver.ExecuteScript(String script, Object[]
args)
       at SeleniumSandbox2.Program.Main(String[] args) in c:\Users\mark.hopwood\Documents\Visual
Studio 2013\Projects\SeleniumSandbox2\SeleniumSandbox2\Program.cs:line 13
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity,
String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException: 

I also see Firefox 35 failing when executing javascript. In the Firefox console, I see
this error: "Security wrapper denied access to property length on privileged Javascript
object. Support for exposing privileged objects to untrusted content via __exposedProps__
is being gradually removed - use WebIDL bindings or Components.utils.cloneInto instead.
Note that only the first denied property access from a given global object will be
reported." This appears to be related to a deprecated javascript property in Firefox:
"http://codeverge.com/mozilla.dev.b2g/notice-do-not-add-new-instances-of-exposedpro/1992161"
 In the file selenium/javascript/firefox-driver/js/firefoxDriver.js I do see a reference
to __exposedProps__. This is making our Firefox Selenium Webdriver testing unusable.
Perhaps this other method Components.utils.cloneInto can be used?

i am also having same above issue,
arguments[0] is undefined
Command duration or timeout: 20 milliseconds
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:03:00'

Tests failing with 'arguments[0] is undefined' in Firefox 35

what i have to do pls help me any one....

I can confirm this issue and downgrading Firefox (for me to version 34.0.5) causes test
scripts to once more work

Same issue here; 34.0.5 works ok.

Same here, v2.44.0 and ff 35.0.1

Hi all -- happening for me also, I cannot execute any JS code with FF 35.0 and Selenium
2.44.0. Is there any fix planned ? Thanks

Same problem with FF35 and selenium 2.43.0

Seeing this issue as well. Downgrading FF to 34.0.5 works. I would say that the priority
of this is perhaps greater than Medium. Our org officially supports the latest version
of FF so until this is fixed our test suites are not running on the latest FF. 

Same issue.  Calls to ExecuteScript are not working properly (triggering UnexpectedJavaScriptError)
and if I watch the Firefox web browser console I see this (as reported previously by
Para.Sel...)

[WEBDRIVER] [INFO] [fxdriver.nsCommandProcessor] Received command: executeScript

Security wrapper denied access to property length on privileged Javascript object.
Support for exposing privileged objects to untrusted content via __exposedProps__ is
being gradually removed - use WebIDL bindings or Components.utils.cloneInto instead.
Note that only the first denied property access from a given global object will be
reported.

Running Selenium Support 2.44.0 and Firefox Portable 35.0

FF 35.0.1, same issue

FF 35.0.1, ubuntu, selenium 2.44 - same issue

Same issue for me too.  Downgrading to FF 34.

Same issue for me.

FF 35.0.1, Macosx Yosemite, selenium 2.44 - same issue

working with FF 34.0.5, selenium 2.44....thank you all

have anyone resolved the issue without downgrading firefox?

same issue here.. is this issue resolved?

@vijay,  there is suppose to be a webdriver dev version that works. I haven't tried
it, though.  I thought I'd see how FF 36 beta worked with the webdriver and it's not
pretty.

This should be increased in priority? Firefox 36 is out in just a week and this is still
broken. This bug is blocking people from effectively testing in recent Firefox versions
:(

FYI - This is merged to 8390.  
https://code.google.com/p/selenium/issues/detail?id=8390