| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Do some refactoring.
Move all stuff about chrome into a sub directory.
Also, delete file chrome_launcher_impl.cc.
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12848005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@188410 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
| |
-Fixes hang when subframes are attached to the DOM before parent frame onload finishes
-Fixes hang where we don't get clearedScheduledNav event during navigation between processes (occasionally)
-Automatically determines load status after connecting. This is helpful for debugging, and critical for connecting to a newly created tab.
BUG=180742, 172942
Review URL: https://codereview.chromium.org/12613011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187622 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When user debugs a testcase with DevTools frontend UI, DevToolsClient will be disconnected. This CL is to automatically close DevTools frontend and reconnect afterwards.
Only try to reconnect before processing a command received from the chromedriver client.
There are two types of frontend UI: one is docked in page, opened through Shift+Ctrl+I or "Tools"--"Developer Tools"; the other is in a new tab, opened with url "chrome-devtools:///...".
For the tab one, we can close it by json/close of DevTools, just like closing a normal page. But for the docked one, we could only close it by clicking a button through Javascript.
BUG=169098
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12321057
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186452 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are still a few additional things needed that I'll fix in following
patches, including changes to navigation waiting for alerts and commands
that are blocked because of alerts.
Also, since we are tracking alerts from each renderer and not the entire browser,
there'll be some weird behavior if multiple renderers have alerts at the same time.
That's just a limitation of the current approach in Chrome, but shouldn't be significant.
BUG=none
Review URL: https://codereview.chromium.org/12314039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@184661 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
Also do the follow refactoring:
1. Refactor class Chrome and ChromeImpl. Added WebView and WebViewImpl which represent windows from the perspective of chromedriver. One Chrome instance has one or more WebViews.
2. Categorize commands into four groups: non-session commands, session commands, window commands, and element commands.
3. Add OnConnected event for lazy initialization of trackers.
4. Wait for pending navigation only when processing Window commands(including Element commands).
BUG=174952
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12086103
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@181743 0039d316-1c4b-4281-b951-d872f2087c98
|
