Cheng Zhao
082aa61870
InspectableWebContents should be able to accept existing WebContents.
2013-04-20 13:24:45 +08:00
Adam Roben
80cb76355c
Update to latest libchromiumcontent
...
* vendor/libchromiumcontent b6a0d85...0d607ee (3):
> Stop trying to compile SQLitePersistentCookieStore separately
> Update to latest Chromium trunk revision
> Merge pull request #4 from aroben/atom
2013-04-17 23:27:53 -04:00
Adam Roben
3c513d6ae8
Remember where the dev tools were docked between launches
2013-04-08 13:53:53 -04:00
Adam Roben
c22d1cca79
Support docking the devtools on the right side of the window
2013-03-27 11:20:21 -04:00
Adam Roben
001d0197de
Make the devtools close button work
2013-03-27 11:20:21 -04:00
Adam Roben
d20ecc0e2b
Merge InspectableWebContentsImpl and DevToolsFrontend
...
While this prevents clients from easily implementing their own devtools
windows, it gives us much easier control over the devtools experience.
2013-03-27 11:20:15 -04:00
Adam Roben
b2a79856ef
Add InspectableWebContents
...
This class can be used to create a content::WebContents that can be inspected
by the Chrome Dev Tools. This requires embedding applications to copy
content_shell.pak into their resource bundle.
Right now the dev tools are always docked to the bottom of the view; we don't
yet support undocking or changing the docked side.
Fixes #1 .
2013-03-14 09:05:42 -04:00
