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; right-click to download) and our HTML-based extensions would integrate better (no need to be stuck in an extra tab on the side with jarringly different UI compared to native controls). On Mon, Sep 28, 2009 at 8:00 PM, Robert Sesek <[email protected]> wrote: > 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 a couple of years ago about something similar. Safari has a helpful tool > in Window --> Activity that allows you to download all resources of a page > (including XHR and others loaded through JS). DevTools does something > similar, but compared to Safari's interface it's slower and harder to find > things (the entries in the list take up more vertical space). > rsesek / @chromium.org > > On Fri, Sep 25, 2009 at 10:25 PM, Ben Goodger (Google) <[email protected]> > wrote: >> >> 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 showing things like: >> >> - general page info in addition to security info >> - web capabilities/permissions used by the page, along with the >> ability to control these, including the effect of any active blacklist >> - media attached to the page, which a convenient way to download >> - eventually an additional surface for extensions to add tabs/features >> based on content-script scanning of the page >> >> The idea anyway is for any web capability there'd be a toggle in here. >> We also envisage some kind of app/extension page where one can visit >> the properties/capabilities for an individual installed app/extension >> too. >> >> Anyway any time the notion of site-specific capability control comes >> up, the response from the UX team tends to be "uber page info window". >> It's on our list, we just have been busy with other stuff. >> >> I mocked this some years ago in Firefox as a bottom bar >> >> http://web.archive.org/web/20051220182808/wiki.mozilla.org/Firefox:Info_Window >> but I am not advocating that approach necessarily. >> >> -Ben >> >> On Fri, Sep 25, 2009 at 7:13 PM, Ben Goodger (Google) <[email protected]> >> wrote: >> > On Fri, Sep 25, 2009 at 6:13 PM, Jeremy Orlow <[email protected]> >> > wrote: >> >> I had the same thoughts. Does Firefox not implement anything like >> >> this? >> >> Another question that this brings up: how could a user un-register >> >> something >> >> even if the web site doesn't do anything to make it possible? In other >> >> words, we might need some piece of UI to remove registrations even >> >> beyond >> >> having an API for it. >> > >> > Uber page info dialog. >> > >> > -Ben >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
