1316454 - WebExtensions: chrome.windows.create causes error messages in Nightly 52.0a1

Status: RESOLVED INVALID

(WebExtensions :: Untriaged, defect)

Description

[dw-dev]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

I have developed a WebExtensions version of my original Tile Tabs add-on. The WebExtensions version is called Tile Tabs WE and was first released in August 2016.

Tile Tabs WE works correctly with Firefox 48.0 through to Firefox 51.0a2, and also with Chrome, without causing any error messages.

However, with Nightly 52.0a1, I am now seeing error messages in the browser console, whenever chrome.windows.create() is called.

For example, executing the following simplified code causes error messages:

    chrome.windows.create({ left: 200, top: 200, width: 400, height: 600 },
    function(newwin)
    {
         if (chrome.runtime.lastError) var message = chrome.runtime.lastError.message;
    });

Adding a 'tabId' or 'url' property still causes the same error messages.




Actual results:

The above code caused the following error messages in the browser console:

    Unchecked lastError value: Error: Invalid tab ID: 4        ExtensionUtils.jsm:399

        withLastError             resource://gre/modules/ExtensionUtils.jsm:399:9
        wrapPromise/<            resource://gre/modules/ExtensionUtils.jsm:450:11




Expected results:

There should not be any error messages.

Comment 1

[Loic]

Could you provide the link to your extension which has the issue, please.

Comment 2

[dw-dev]

I have done some more testing and have discovered that my test environment for Nightly 52.0a1 was set up differently to those for Firefox 48.0 through Firefox 51.0a2.

This means that the error messages I had seen were not related to chrome.windows.create(), but in fact are related to chrome.tabs.move() and chrome.tabs.onZoomChange.addListener().

Since the bug description is now very different from the description in this bug report, I have decided to raise a new bug 1316907.

Please can you mark this bug report as invalid and close.