Closed Bug 187908 Opened 22 years ago Closed 22 years ago

In <pageInfo.js>, "Warning: reference to undefined property item.href"

Categories

(SeaMonkey :: Page Info, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: db48x)

Details

Attachments

(3 files, 1 obsolete file)

if you try to save an image that doesnt exist: Warning: reference to undefined property item.href Source File: chrome://navigator/content/pageInfo.js Line: 718 20030105
WFM in the latest Windows nightly; perhaps this has been fixed by the other pageinfo changes?
not fixed: Warning: reference to undefined property item.href Source File: chrome://navigator/content/pageInfo.js Line: 739 if you press Save As on an image that doesnt exist. 20030320
Attached file testcase
Steps to Reproduce: 1. Open attached HTML page 2. Go to View | Page Info 3. Click on the Media tab 4. Click on the Save As... button
Attached patch patch (obsolete) — Splinter Review
Attachment #118200 - Flags: review?(db48x)
Comment on attachment 118200 [details] [diff] [review] patch you need to change both null checks. It also has nothing to do with whether the image is missing or not, but it's a bug none the less.
Attachment #118200 - Flags: review?(db48x) → review-
Attachment #118200 - Attachment is obsolete: true
Attachment #118212 - Flags: review?(db48x)
Comment on attachment 118212 [details] [diff] [review] patch to fix both null checks looks good
Attachment #118212 - Flags: superreview+
Comment on attachment 118212 [details] [diff] [review] patch to fix both null checks oops, my bad
Attachment #118212 - Flags: review?(db48x)
Attachment #118212 - Flags: superreview+ → review+
Attachment #118212 - Flags: superreview?
Attachment #118212 - Flags: superreview? → superreview?(alecf)
Comment on attachment 118212 [details] [diff] [review] patch to fix both null checks how about if ("href" in item && item.href) (the null is redundant, IMO)
Attachment #118212 - Flags: superreview?(alecf) → superreview+
> if ("href" in item && item.href) I agree. Looking through the code, this is the convention used most often. What should I do -- create a new patch? Sorry, I'm a n00b at patches.
yea, go ahead and make another patch. makes it easier for to get someone to check it in :)
Here's the patch with the != null removed. Could someone check this in for me? I don't have CVS access.
Attachment #118212 - Flags: approval1.4b?
Comment on attachment 119469 [details] [diff] [review] final patch with != null removed carrying over r/sr. here's your a=sspitzer
Attachment #119469 - Flags: approval1.4b+
Attachment #119469 - Flags: approval1.4?
what happened here? did this have r/sr/a for 1.4 beta, but never checked in?
yep. I should have thought about it and asked in irc, that usually works.
Comment on attachment 119469 [details] [diff] [review] final patch with != null removed a=asa (on behalf of drivers) for checkin to 1.4.
Attachment #119469 - Flags: approval1.4? → approval1.4+
timeless just checked this in
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Summary: strict javascript warning in pageInfo.js → In <pageInfo.js>, "Warning: reference to undefined property item.href"
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: