Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core extensions are loaded 2x - document this, or prevent it #1549

Closed
peter-lyons-kehl opened this issue Jan 28, 2016 · 1 comment
Closed
Labels

Comments

@peter-lyons-kehl
Copy link

  1. Have Selenium IDE 2.4.0 in Firefox 25
  2. Have a Core extension in a ,js file, specify it at IDE > Options > Options > core extensions (and restart Selenium)
  3. The file will be loaded/processed (at least) twice
  4. first, at IDE startup
  5. second, the first time I run any Selenese command
    See stacktraces below.

This may not affect simple usage. But it is badly confusing if your Core extension creates objects via XPCOM or JS component, SQLite connection, a file etc. - objects that need to be tracked or released, or that are book kept somehow.

Action needed: Either

Example of stack trace in Selenium IDE 2.9.1:

At srtart of Selenium IDE:
@chrome://selenium-ide/content/tools.js -> file:///tmp/core-extension.js?1453953484869:3:6
ExtensionsLoader.loadSubScript/<@chrome://selenium-ide/content/tools.js:206:11
ExtensionsLoader.loadSubScript@chrome://selenium-ide/content/tools.js:203:5
Editor.prototype.loadSeleniumAPI@chrome://selenium-ide/content/editor.js:1128:7
Editor@chrome://selenium-ide/content/editor.js:164:3
StandaloneEditor@chrome://selenium-ide/content/standalone-editor.js:22:5
onload@chrome://selenium-ide/content/selenium-ide.xul:1:1

First Selenese command run:
@chrome://selenium-ide/content/tools.js -> file:///tmp/core-extension.js?1453953493781:3:6
ExtensionsLoader.loadSubScript/<@chrome://selenium-ide/content/tools.js:206:11
ExtensionsLoader.loadSubScript@chrome://selenium-ide/content/tools.js:203:5
Debugger/this.init@chrome://selenium-ide/content/debugger.js:66:9
Debugger.prototype.executeCommand@chrome://selenium-ide/content/debugger.js:171:3
.executeCurrentCommand@chrome://selenium-ide/content/treeView.js:523:21
.initialize/controller.doCommand@chrome://selenium-ide/content/treeView.js:84:55
goDoCommand@chrome://global/content/globalOverlay.js:96:7
ondblclick@chrome://selenium-ide/content/selenium-ide.xul:1:1

(Originally reported as https://code.google.com/p/selenium/issues/detail?id=6697.)

@barancev
Copy link
Member

Selenium IDE development has been discontinued. No more new features and no bug fixes. From Firefox 55 onwards, Selenium IDE will no longer work [1]. The last supported version is Firefox ESR 52.

Yes, we've started a project to develop a new tool that should replace Selenium IDE. Follow #4406 for the progress.

Sorry this issue has not beed properly and timely addressed, and thank you for submission!

[1] https://seleniumhq.wordpress.com/2017/08/09/firefox-55-and-selenium-ide/

@lock lock bot locked and limited conversation to collaborators Aug 17, 2019
@lock lock bot unassigned samitbadle Aug 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants