Closed
Bug 1125501
Opened 10 years ago
Closed 10 years ago
TypeError: impl is null network-monitor.js:97:6
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: regression)
Steps to reproduce:
1. Install https://addons.mozilla.org/en-US/firefox/addon/foxyproxy-standard/ and restart
2. Open Browser Console (Ctrl+Shift+J)
3. Right click on toolbar icon. And choose "Use proxies based on their pre-defined patterns and priorities" to enable add-on
4. Open https://addons.mozilla.org/en-US/firefox/?utm_source=snippet&utm_medium=snippet&utm_campaign=addons
Actual Results:
TypeError: impl is null network-monitor.js:97:6
Regression window
Good:
https://hg.mozilla.org/integration/mozilla-inbound/rev/93976782a910
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150122052129
Bad:
https://hg.mozilla.org/integration/mozilla-inbound/rev/174cc41e7e03
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150122054047
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=93976782a910&tochange=174cc41e7e03
Triggered by:
2d8d90eaab6e J. Ryan Stinnett — Bug 731318 - Show transferred size in Net Monitor. r=vporof
Does the addon still function as expected?
Flags: needinfo?(alice0775)
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to J. Ryan Stinnett [:jryans] from comment #1)
> Does the addon still function as expected?
No, it is not working
Flags: needinfo?(alice0775)
Reporter | ||
Comment 3•10 years ago
|
||
Probably, Bug 1125372.
(In reply to Alice0775 White from comment #3)
> Probably, Bug 1125372.
Can you confirm that it now works correctly after bug 1125372 is resolved?
I just want to be sure that this bug is just about a log message and not functionality.
Flags: needinfo?(alice0775)
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to J. Ryan Stinnett [:jryans] from comment #4)
> (In reply to Alice0775 White from comment #3)
> > Probably, Bug 1125372.
>
> Can you confirm that it now works correctly after bug 1125372 is resolved?
>
> I just want to be sure that this bug is just about a log message and not
> functionality.
FoxyProxy does not work. Bug 1125372 does not fix....
Tested with latest m-c tinderbox
https://hg.mozilla.org/mozilla-central/rev/fc21937ca612
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150128052133
Flags: needinfo?(alice0775)
(In reply to Alice0775 White from comment #5)
> (In reply to J. Ryan Stinnett [:jryans] from comment #4)
> > (In reply to Alice0775 White from comment #3)
> > > Probably, Bug 1125372.
> >
> > Can you confirm that it now works correctly after bug 1125372 is resolved?
> >
> > I just want to be sure that this bug is just about a log message and not
> > functionality.
>
> FoxyProxy does not work. Bug 1125372 does not fix....
>
> Tested with latest m-c tinderbox
> https://hg.mozilla.org/mozilla-central/rev/fc21937ca612
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
> ID:20150128052133
Here are the results of my local testing with a recent copy of fx-team (2015-01-28) (http://hg.mozilla.org/integration/fx-team/rev/42750f461e95) and FoxyProxy 4.5:
* Choosing a proxy to use "for all URLs" works, but "Use proxies based on their patterns" does not appear to work
* Reverting bug 731318 does stop the TypeError from being logged, however it does not fix "Use proxies based on their patterns"
I am happy to clean up the TypeError here, but it appears bug 731318 is not the root cause of FoxyProxy's broken functionality.
I did a minimal investigation of FoxyProxy which agrees with the FoxyProxy forum[1] that the functionality issue is caused by bug 436344, and it's likely that the FoxyProxy developers need to update the add-on to account for this change.
[1]: http://forums.getfoxyproxy.org/viewtopic.php?f=4&t=1251
Reporter | ||
Comment 7•10 years ago
|
||
See http://forums.mozillazine.org/viewtopic.php?f=38&t=2859425
version 2.2.4 Works fine.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 8•10 years ago
|
||
Mistakenly filed against Firefox 38 and should be instead 38 Branch. Sorry for the spam. dkl
Version: Firefox 38 → 38 Branch
I have Firefox 40 Beta and still have this error.
FoxyProxy works in my setup (Use proxies based on their pre-defined patterns and priorities)
You need to log in
before you can comment on or make changes to this bug.
Description
•