Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Problems with firefox 15 #4486

Closed
lukeis opened this issue Mar 4, 2016 · 10 comments
Closed

Problems with firefox 15 #4486

lukeis opened this issue Mar 4, 2016 · 10 comments
Assignees
@lukeis
Labels
Browser-Firefox Component-WebDriver Priority-Medium Restrict-AddIssueComment-Commit Status-Duplicate Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 4, 2016

Originally reported on Google Code with ID 4486

After the click the site is reloaded.
With firefox 14 run well, with 15 no.
Other clickandwait over hyperlink run well in both versions

With firefox 14

clickAndWait    Aceptar     60000
pause   2000    
selectFrame     relative=up     
selectFrame     folder  

with firefox 15

clickAndWait    Aceptar     can't access dead object
pause   2000    
selectFrame     relative=up     Command execution failure. Please search the user group at
https://groups.google.com/forum/#!forum/selenium-users for error details from the log
window.  The error message is: can't access dead object
selectFrame     folder  


Selenium version: ide 1.9 jar 2.25.0
OS: windows 2003 server
Browser: firefox
Browser version: 14 & 15

Reported by eluqueunca on 2012-08-30 12:56:18
@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Actions working on Firefox 14 no longer work on Firefox 15.
For instance:

(...)
driver.get("http://www.google.com");
Actions builder = new Actions(driver);
builder.moveToElement(driver.findElement(By.xpath("//div[@class='jsb']//input[1]"))).perform();
(...)

doesn't highlight the "Google Search" button, but it worked with Firefox 14 and works
with Chrome

Reported by g.trevisti on 2012-09-03 13:17:49

@lukeis lukeis self-assigned this Mar 4, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Yeah, I seem to be having problems with this as well... 2.24.1

Reported by billapepper on 2012-09-10 14:03:48

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

This issue will be fixed in 2.26

Reported by barancev on 2012-09-11 09:10:50

  • Labels added: Component-WebDriver, Browser-Firefox

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Thank barancev, 

Is there an ETA for 2.26? Is there a release schedule somewhere?

Reported by billapepper on 2012-09-11 12:20:19

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Selenium 2.24.1 does not support "native events" for Firefox 14+, which definitely affected
my ability to click on elements. Upgrading to Selenium 2.25.0 fixed my problems with
Firefox 14.0.1, although everything broke again when Firefox 15 was released. I have
currently been forced to downgrade to Firefox 14.0.1.

Reported by rankincj on 2012-09-12 08:16:38

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reported by barancev on 2012-09-27 19:18:31

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Must confirm this bug, on Firefox 16 and Selenium 2.25.0.
Waiting for Selenium 2.26.

Thanks :D

Reported by potdelard@hotmail.com on 2012-10-10 18:30:22

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

Firefox 16.0.1
[error] isNewPageLoaded found an old pageLoadError: TypeError: can't access dead object
[warn] Stack is: @chrome://selenium-ide/content/selenium-core/scripts/atoms.js:8762
@chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js:1204 @chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js:942
@chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js:1080 @chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js:1090
@chrome://selenium-ide/content/selenium-core/scripts/selenium-executionloop.js:138
@chrome://selenium-ide/content/selenium-runner.js:133 @chrome://selenium-ide/content/selenium-core/scripts/htmlutils.js:60
[error] can't access dead object
[info] Executing: |pause | 2000 | |
[info] Executing: |selectFrame | relative=up | |
[error] Unexpected Exception: fileName -> chrome://selenium-ide/content/selenium-core/scripts/atoms.js,
lineNumber -> 8762

Reported by eluqueunca on 2012-10-12 16:29:34

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016 

THIS IS NOT FIXED.

Just found this exact same problem with 2.33.

PHP Code:

$this->assertElementPresent("name=save_details");
$this->clickAndWait("name=save_details");

First line works fine - it asserts the element is there. Second line gives the can't
access dead object error. Looks like Selenium is caching the reference to the object
so it finds it "present", but Firefox won't let it interact as it doesn't exist any
more.

Anyone got a suggestion how I force selenium to rescan the document? It's been over
a year since I've been able to run a test.

Reported by hippyjim on 2013-06-25 14:15:55

@lukeis
Copy link
Member Author

lukeis commented Mar 4, 2016

Reported by luke.semerau on 2015-09-17 18:16:07

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 4, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lukeis lukeis

Labels
Browser-Firefox Component-WebDriver Priority-Medium Restrict-AddIssueComment-Commit Status-Duplicate Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis