140899 - Page Info does not display Links or Media information.

Status: RESOLVED DUPLICATE of bug 170143

(SeaMonkey :: Page Info, defect)

Description

[Jeremy]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0rc1) Gecko/20020417
BuildID:    2002041711

The Page Info function displays no information about the links or the images on
this page.

Reproducible: Always
Steps to Reproduce:
1.View->Page Info
2.Select Links or Media


Actual Results:  Blank fields display no Links or Media information.

Expected Results:  Should see list of all links on page and image/icon information.

Broken in 0.9.9 also. Equivalent function worked in v0.9.8

Comment 1

[Adrian Ulrich]

wfm 2002042423 on linux

Comment 2

[Daniel Brooks [:db48x]]

Jeremy, do you see any errors in the JS Console when you experience this problem?

Comment 3

[alge]

I see this in a cvs build on linux, with js errors:

link page:

Error: aDocument.hasAttributeNS is not a function
Source File: chrome://navigator/content/pageInfo.js
Line: 510
Error: uncaught exception: [Exception... "'[JavaScript Error:
"aDocument.hasAttributeNS is not a function" {file:
"chrome://navigator/content/pageInfo.js" line: 510}]' when calling method:
[nsIDOMNodeFilter::acceptNode]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://navigator/content/pageInfo.js :: grabAllXLinks :: line 521"  data: yes]

media page:

Error: elem.nodeName has no properties
Source File: chrome://navigator/content/pageInfo.js
Line: 559

Comment 4

[Jeremy]

Similar to Comment #3, I get these three error messages in a "clean" JS Console
when loading the web-page. (This is under WinNT)

-----------------------------------------------------
Error: aDocument.hasAttributeNS is not a function
Source File: chrome://navigator/content/pageInfo.js
Line: 505
-----------------------------------------------------
Error: uncaught exception: [Exception... "'[JavaScript Error:
"aDocument.hasAttributeNS is not a function" {file:
"chrome://navigator/content/pageInfo.js" line: 505}]' when calling method:
[nsIDOMNodeFilter::acceptNode]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://navigator/content/pageInfo.js :: grabAllXLinks :: line 516"  data: yes]
-----------------------------------------------------
Error: elem.nodeName has no properties
Source File: chrome://navigator/content/pageInfo.js
Line: 554
-----------------------------------------------------

Comment 5

[Adam Hauner]

Confirming using 2002043003/trunk/Win2K with same JS error.

Error in JS looks same as error in comment #1 of bug 136539.

Daniel: All these bugs about nothing shown in Media Tab and crashes on Page Info
are IMHO related to Java applets. 

Comment 6

[John Morrison]

When Java is enabled, the DOM model for <APPLET> is completely broken. Bug 
#59686 and others.

Comment 7

[Mikhail Sogrine]

In build 2002092108 Win2K, when I open Page Info I see (it happens even for
Mozilla home page):

Error: elem.nodeName has no properties
Source File: chrome://navigator/content/pageInfo.js

Line is different for different tabs: 319 (Forms), 470 (Links), 633 (Media)

Comment 8

[Adam Hauner]

Mikhail: see bug 170143 (it's reason of JS error).

Comment 9

[Daniel Brooks [:db48x]]

dup

*** This bug has been marked as a duplicate of 170143 ***