This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
ElementFinders should work as params in executeScript calls #1600
Comments
This is probably due to f7c3c37 (which is listed as a breaking change in the CHANGELOG) Fortunately, there's a more concise way to fix this. See an example test at 862a096 Your code would look like: it('should scroll into an unhindering page view of all checkboxes', function() {
var bottomElement = element.all(by.css('p.note')).last();
browser.driver.executeScript("arguments[0].scrollIntoView(true);", bottomElement.getWebElement());
}); |
However, I'm leaving this issue open because this is hard to discover and it would be great if you didn't have to use the |
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Jan 7, 2015
* reuse logic for browser.pause for elementExplorer * introduce browser.enterRepl * allow customization of driver for elementExplorer * fix bug where repl cannot return an ElementFinder (related angular#1600) Closes angular#1314, angular#1315
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Jan 7, 2015
* reuse logic for browser.pause for elementExplorer * introduce browser.enterRepl * allow customization of driver for elementExplorer * fix bug where repl cannot return an ElementFinder (related angular#1600) Closes angular#1314, angular#1315
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Jan 7, 2015
* reuse logic for browser.pause for elementExplorer * introduce browser.enterRepl * allow customization of driver for elementExplorer * fix bug where repl cannot return an ElementFinder (related angular#1600) Closes angular#1314, angular#1315
hankduan
added a commit
to hankduan/protractor
that referenced
this issue
Jan 13, 2015
* reuse logic for browser.pause for elementExplorer * introduce browser.enterRepl * allow customization of driver for elementExplorer * fix bug where repl cannot return an ElementFinder (related angular#1600) Closes angular#1314, angular#1315
juliemr
changed the title
element(.css()) & browser.driver.executeScript(s) causing infinite loop after protractor update
ElementFinders should work as params in executeScript calls
Mar 17, 2015
@mgiambalvo I'm not sure if this works now or not, can you check and let's figure out a workaround if not. |
This was referenced Jul 14, 2016
It works now! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The following code causes infinite loop on the selector, i.e :
12:15:11.418 INFO - Executing: [find elements: By.selector: p.note])
12:15:11.424 INFO - Done: [find elements: By.selector: p.note]
or
or
_browser.executeScript()_ does the same thing. If I remove the execute script, the code no longer loops infinitely through the selector.
_Note: This was working fine prior to the 1.4.0 update from 1.2.0~_
Any ideas?
The text was updated successfully, but these errors were encountered: