User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170307064827 Steps to reproduce: re: Bug 1343444 Initially, I requested an API support for addTabsProgressListener. I have been told to file the API request under WebNavigation API bug. It was asserted that the support is already provided in WebNavigation API. However, it turned out to be missing. > My addon (Refresh Blocker) requires 'onRefreshAttempted' from 'addTabsProgressListener'. It is the only working addon in this category and AFAIK none of the other browser have it due to the absence of an API. I would like to be able to migrate the addon to WebExtension if an API could be implemented. > From what I understand from the documentatons, webNavigation.onCommitted has transitionQualifiers property. onCommitted is fired when a navigation is committed. At least part of the new document has been received from the server and the browser has decided to switch to the new document. > It is fired too late and does not cover the function of 'onRefreshAttempted' from 'addTabsProgressListener'. > webNavigation.onBeforeNavigate may have been appropriate but it does not have a transitionQualifiers property. > Additionally, necessary details such as aRefreshURI, aMillis, aSameURI are not provided by the transitionQualifiers property. It is worth notion that 'onRefreshAttempted' from 'addTabsProgressListener' is fired when a page loads, and not when a page it about to re-navigate. In other words, after a page is loaded with a meta refresh for 10 minutes later, 'onRefreshAttempted' is fired and can be dealt with, not when it is about to refresh (10 minutes after the page is loaded). The WebNavigation API appears to deal with navigation differently than addTabsProgressListener.
This has been added to the agenda for the April 4 WebExtensions triage. Erosman, will you be able to attend? Call-in information can be found here: https://wiki.mozilla.org/Add-ons/Contribute/Triage Meeting agenda can be found here: https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit#heading=h.du5ihvu5p6ro
This issue has been discussed in the WebExtensions API triage meeting and it has been approved. The only concern showed by the participants during the meeting is related to where this feature would better placed (webNavigation or webRequest)