browser.xml refers to bogus property nsIWebNavigation.LOAD_FLAGS_BYPASS_NONE

VERIFIED FIXED

Status

()

VERIFIED FIXED
17 years ago
17 years ago

People

(Reporter: bugzilla, Assigned: jag-mozilla)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Rightclicking on a link and choosing open in a new tab produces:

Warning: reference to undefined property nsIWebNavigation.LOAD_FLAGS_BYPASS_NONE
Source File: chrome://global/content/bindings/browser.xml#browser.loadURI()
Line: 2

You should turn on javascript strict warnings in the "Edit -> Prefs -> Debug" 
so we could avoid all the strict warning fixup...!

Comment 1

17 years ago
-> xpt
Assignee: asa → hyatt
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm

Comment 2

17 years ago
Hmm, looks like this one should definitely be cleaned up. There is indeed no 
such property 'LOAD_FLAGS_BYPASS_NONE' on the nsIWebNavigation interface, 
which means we are passing 'undefined' as the flags value in those calls to 
nsIWebNavigation. That's not good.
 http://lxr.mozilla.org/seamonkey/search?string=LOAD_FLAGS_BYPASS_NONE
Assignee: hyatt → jaggernaut

Updated

17 years ago
Summary: javascript strict warnings in browser.xml → browser.xml refers to bogus property nsIWebNavigation.LOAD_FLAGS_BYPASS_NONE
(Assignee)

Comment 3

17 years ago
Created attachment 51436 [details] [diff] [review]
Simple fix.

Comment 4

17 years ago
Comment on attachment 51436 [details] [diff] [review]
Simple fix.

r=rginda
Attachment #51436 - Flags: review+

Comment 5

17 years ago
checked in, rev 1.7, marking fixed.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

17 years ago
Thanks John.

Comment 7

17 years ago
No, thank you, dude!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.