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

TypeError: "alert" is read-only Firefox #52

Closed
corevo opened this issue Nov 23, 2017 · 6 comments
Closed

TypeError: "alert" is read-only Firefox #52

corevo opened this issue Nov 23, 2017 · 6 comments
Labels
blocked-by-v4 Issues and PRs blocked by v4 help wanted

Comments

@corevo
Copy link
Member

corevo commented Nov 23, 2017

Firefox does not let monkey patching the alert, which causes incompatibility with alert using test cases

@jakehm
Copy link

jakehm commented Dec 6, 2017

I am getting this error on every page even when selenium ide isn't actually open.
This is on firefox nightly:

TypeError
columnNumber: 232
fileName: "moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js"
lineNumber: 2820
message: "\"alert\" is read-only"
stack: "./selenium-browserbot.js/BrowserBot.prototype.modifyWindowToRecordPopUpDialogs@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:2820:232\n./selenium-browserbot.js/BrowserBot.prototype._modifyWindow@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:2773:44\n./selenium-browserbot.js/BrowserBot.prototype.getCurrentWindow@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:2914:524\n./selenium-browserbot.js/BrowserBot.createForWindow@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:2701:50\n./commands-api.js@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:967:834\n__webpack_require__@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:30:12\n./record-api.js@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:1115:326\n__webpack_require__@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:30:12\n./record.js@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:1140:292\n__webpack_require__@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:30:12\n[4]@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:3157:18\n__webpack_require__@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:30:12\n@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:73:18\n@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:11:18\nwebpackUniversalModuleDefinition@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:7:11\n@moz-extension://35444d37-3417-4f83-8bd0-cadee41713b9/assets/record.js:1:11\n"

Is it related?

@corevo
Copy link
Member Author

corevo commented Dec 6, 2017

Yes it is, the extension is preparing every page to be tested regardless of wether the window is open or not, its a behavior I'm planning on changing.
That error happens specifically due to firefox not letting me rebind window.alert so that I can record the calls to it

@justnewbee
Copy link

i would like to report this too, it gets very annoying, please fix this
btw, selenium-ide is cool, thank you

@toddtarsi toddtarsi added the blocked-by-v4 Issues and PRs blocked by v4 label Nov 27, 2021
@toddtarsi
Copy link
Contributor

Noting here, the fix for this is to finish the re-write of Selenium IDE v4 in Electron / Node.

@toddtarsi
Copy link
Contributor

Closing, v4 is in alpha now

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked-by-v4 Issues and PRs blocked by v4 help wanted
Projects
None yet
Development

No branches or pull requests

4 participants