This repository was 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
Have element-explorer use embedded chrome driver #1315
Labels
Comments
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
After #1693, you can enter element explorer via flag |
this is seriously neat! |
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
Done at #1693 (comment) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I really like the option to use the embedded chrome driver for protractor. It would be very convenient to be able to use the same in the element-explorer.
The text was updated successfully, but these errors were encountered: