On Thu, Aug 13, 2009 at 1:18 PM, Tim Steele t...@chromium.org wrote:
and use a RenderViewHost directly. The personalization code used to do
something like this using a thing I added called HWNDHtmlView. I think
extensions used it for a while, and there was a bug+todo there to try and
Thanks for the speedy response guys. I got the impression chrome-resource
is coupled to the new tab page from stuff like this:
// Special case the new tab page. In older versions of Chrome, the new tab
// page was hosted at chrome-internal:blah. This might be in people's
saved
// sessions or
On Thu, Aug 13, 2009 at 3:11 PM, Tim Steele t...@chromium.org wrote:
On Thu, Aug 13, 2009 at 2:56 PM, Tim Steele t...@chromium.org wrote:
Thanks for the speedy response guys. I got the impression chrome-resource
is coupled to the new tab page from stuff like this:
hm. make that
I think that rather than having a scheme that opens a dialog, we should make
the HTML dialog open any URL you give it. Then you can just re-use chrome://
which is used by the NTP etc.
-Ben
On Thu, Aug 13, 2009 at 1:18 PM, Tim Steele t...@chromium.org wrote:
Currently most of the code for
