Closed
Bug 399746
Opened 17 years ago
Closed 17 years ago
Exception... "'[JavaScript Error: "gImageView.data[i] has no properties" {file: "chrome://browser/content/pageinfo/pageInfo.js" line: 554}]' when calling method: [nsIDOMNodeFilter::acceptNode]"
Categories
(Firefox :: Page Info Window, defect)
Firefox
Page Info Window
Tracking
()
RESOLVED
FIXED
People
(Reporter: reed, Assigned: florian)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
2.29 KB,
patch
|
asaf
:
review+
db48x
:
review+
beltzner
:
approval1.9+
|
Details | Diff | Splinter Review |
Got this exception when I opened the Page Info window today: Error: uncaught exception: [Exception... "'[JavaScript Error: "gImageView.data[i] has no properties" {file: "chrome://browser/content/pageinfo/pageInfo.js" line: 554}]' when calling method: [nsIDOMNodeFilter::acceptNode]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: chrome://browser/content/pageinfo/pageInfo.js :: doGrab :: line 499" data: yes]
Flags: blocking-firefox3?
Assignee | ||
Comment 1•17 years ago
|
||
Do you have some steps to reproduce? The url of the page?
Comment 2•17 years ago
|
||
I can't easily reproduce: Reed, can you provide more details on how to see this exception?
Flags: blocking-firefox3?
Reporter | ||
Comment 3•17 years ago
|
||
I came across this again today. Here's my STR: 1. Visit http://news.bbc.co.uk/2/hi/asia-pacific/7132886.stm 2. Open Page Info dialog 3. See error in error console Florian, how's that?
Reporter | ||
Comment 4•17 years ago
|
||
Oh, the error has changed a bit now. Error: uncaught exception: [Exception... "'[JavaScript Error: "gImageView.data[i] is undefined" {file: "chrome://browser/content/pageinfo/pageInfo.js" line: 556}]' when calling method: [nsIDOMNodeFilter::acceptNode]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: chrome://browser/content/pageinfo/pageInfo.js :: doGrab :: line 501" data: yes]
Comment 5•17 years ago
|
||
mmm, that's an interesting error.
Assignee | ||
Comment 6•17 years ago
|
||
Apparently we get screwed because |"watch" in { }| returns true.
Assignee | ||
Comment 7•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Attachment #292698 -
Flags: review?(db48x)
Comment 9•17 years ago
|
||
Comment on attachment 292698 [details] [diff] [review] patch v1 r=db48x
Attachment #292698 -
Flags: review?(db48x) → review+
Comment 10•17 years ago
|
||
Comment on attachment 292698 [details] [diff] [review] patch v1 r=mano
Attachment #292698 -
Flags: review?(mano) → review+
Reporter | ||
Comment 11•17 years ago
|
||
Comment on attachment 292698 [details] [diff] [review] patch v1 Fixes a JS exception due to use of JS-reserved word.
Attachment #292698 -
Flags: approval1.9?
Comment 12•17 years ago
|
||
Comment on attachment 292698 [details] [diff] [review] patch v1 a=beltzner
Attachment #292698 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 13•17 years ago
|
||
Fixed for both Firefox and SeaMonkey. Checking in browser/base/content/pageinfo/pageInfo.js; /cvsroot/mozilla/browser/base/content/pageinfo/pageInfo.js,v <-- pageInfo.js new revision: 1.11; previous revision: 1.10 done Checking in suite/browser/pageinfo/pageInfo.js; /cvsroot/mozilla/suite/browser/pageinfo/pageInfo.js,v <-- pageInfo.js new revision: 1.4; previous revision: 1.3 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•