235065 - Saving about:plugins does nothing useful

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Tim Powell]

Type about:plugins in the address box or use Help->About Plug-ins.
Save the page (either web page complete or just html).
Open the saved page.

Expected:
See basically the same page you just had.

Actual:
Nothing seems to happen.

Observed in Mozilla 1.6 and Firefox 0.8 releases.

It appears that about:plugins is generated using JavaScript and is granted
special privileges to get the list. These aren't granted (and shouldn't be) when
viewing the page as HTML. 

I'm trying to diagnose a problem with a remote customer and I want to get the
current information about the browser configuration. I wanted to just have him
send me the saved about:plugins page. It'd be nice we could save the processed
result instead of the raw JavaScript code. Is this a problem with all JavaScript
generated pages?

Would this be fixed by bug 186490? I'd imagine if about:plugins was generated by
C++, we'd just get raw HTML instead of fancy JavaScript. But it sounds like the
C++ version isn't going to happen.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> It'd be nice we could save the processed result instead of the raw JavaScript
> code.

That's what saving as "web page, complete" will give you....

Comment 2

[Tim Powell]

> > It'd be nice we could save the processed result instead of the raw 
> > JavaScript code.
> That's what saving as "web page, complete" will give you....

Really? Hmmm... Yep, it sure does. I thought I had tried both.

Looks like this bug worksforme. I can certainly get a meaningful result saving
with Web Page, Complete.

Does "web page, complete" always give a processed result? If so, that has not
been clear to me. I always thought the complete meant with images and other
files as compared to the "web page, html only". I knew it changed the URLs to
map to the downloaded files, but didn't think it was a processed version. Is the
HTML only one also a processed result instead of what's sent from the server?
I'm guessing no. I'd almost like to see "web page, HTML only" give a processed
version (basically the HTML part of the complete version) and add an item for
"web page, html only (unprocessed)".

Well, it seems that this bug was caused by me misunderstanding the difference
between the types of save. I thought the only difference between Web Page
Complete and Web Page HTML only was just in how many files you'd end up with. It
seems there's another variable at play here. I won't morph this bug into one
about changing behavior, or debating menu naming conventions, or adding menu
items, although I would like clarification about what the current ones do so it
doesn't trip me up again. Thanks.

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420