1421250 - "filter.onstop" is fired after calling filter.close()

Status: NEW

(WebExtensions :: Request Handling, defect, P3)

Description

[CosminB]

[Affected versions]:
- Firefox 59.0a1 (20171127220446)
- Firefox 58.0b7 (20171127135700)

[Affected platforms]:
- Ubuntu 14.0.4 32-bit
- Mac OS X 10.13.1

[Steps to reproduce]:
1.Load the attached extension in about:debugging.
2.Open example.com page.
3.Click on the extensions icon.
4.Refresh the example.com page.
5.Click on the extension icon.
6.Repeat step 4 and 5 a few times.
7.Observe the browser console.

[Expected results]:
- The next logs are not displayed in the browser console.
filter.onstop
"filter.status must be "closed", but is "finishedtransferringdata" - https://bugzil.la/1405375"

[Actual results]:
- After some refreshes of the example.com page the "filter.onstop" is fired after calling filter.close().

On Windows 7 64-bit I was not able to reproduce the issue.

Please see the attached video.

Comment 1

[CosminB]

Here is the video: https://drive.google.com/file/d/1wCONTzJIHc_hNejj-t7ZfatkAwGAHZrD/view?usp=sharing

Comment 2

[CosminB]

The documentation says that after filter.close(), "no more filter events will be given to the extension."
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest/StreamFilter/close