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 granular per-page prefs. What's changed?
-Nick On Fri, Sep 25, 2009 at 7: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 -~----------~----~----~----~------~----~------~--~---
