I'd like to suggest early on that it's done in HTML for the usual
reasons. (And also that there are the usual negatives. Just wanna
plant the seed.)
In particular, a meta-page page would allow the typical operations on
subresource links (click to view; media playing would work in-browser;
Good point on HTML. Why not instead make DevTools
better/faster/do-what-you-want-them-to-do?
:DG
On Tue, Sep 29, 2009 at 9:08 AM, Evan Martin e...@chromium.org wrote:
I'd like to suggest early on that it's done in HTML for the usual
reasons. (And also that there are the usual negatives.
Depends if we want it to feel webby or dialoggy. Unsure yet. Good case
for either way. Will keep it in mind.
-Ben
On Tue, Sep 29, 2009 at 9:08 AM, Evan Martin e...@chromium.org wrote:
I'd like to suggest early on that it's done in HTML for the usual
reasons. (And also that there are the
I agree that this comes up often enough that it's probably worth doing. The
opportunities for extensions that you mention are also interesting. I don't
see how this would make it into 4.0, but maybe something to prioritize for
5.0?
Out of curiosity, you've historically been opposed to any kind of
For reference: http://code.google.com/p/chromium/issues/detail?id=5973
I'd be interested in helping out with this on the Mac side. I filed a Camino
bug https://bugzilla.mozilla.org/show_bug.cgi?id=297376 a couple of years
ago about something similar. Safari has a helpful tool in Window --
BTW I should note what I mean by Uber Page Info Window.
For some time, we've talked about improving the page info window in
Chrome. Right now it shows only the security information for a SSL
page. In the future we'd like to extend this to show other
information. The idea is there'd be a few tabs