As part of UI unification, page info should become in-content or at least appears in a sidebar. I also remember an old mockup (http://stephenhorlander.com/pages/sketchy-stuff/fullscreen-sketches.jpg) where page info was integrated to the identity panel. It could be another solution.

This doesn't make sense. Part of the utility of Page Info is that it exists as a separate window. What sort of gains do we expect that offsets the loss of functionality?

In fact it makes perfect sense to have the ability to check page info (for example as a sidebar) while navigating on the page itself and killing separate windows should be a long term goal.

> In fact it makes perfect sense to have the ability to check page info (for example as a > sidebar) And in fact my extension xSidebar does allow you to have the Page Info window in a sidebar, but sometimes it's really useful to have a separate PageInfo window when comparing two tabs for example.

(In reply to Philip Chee from comment #3) > And in fact my extension xSidebar does allow you to have the Page Info > window in a sidebar, but sometimes it's really useful to have a separate > PageInfo window when comparing two tabs for example. I agree. I would add that the media pane of Page Info--which is arguably its most widely-used feature--would not integrate well into a sidebar in many cases. I raised this issue several years ago and suggested that Page Info actually be a content page like about:addons, but the UI team couldn't come to a consensus about how to redesign Page Info without losing functionality, and the idea was shelved indefinitely. Page Info may still use an older UI and feel a somewhat different than the direction Firefox has been going for several years, but it is still highly serviceable and any radical change to it needs to be very, very carefully approached and should represent a strong consensus between the UI team, Firefox peers, and long-time Page Info developers.

I don't think it's happening anytime soon so marking as worksome. "Page info" will need redesign in the future though.

WORKSFORME means: "All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened."