Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-Misc New issue 25001 by [email protected]: Extensions API methods have optional params before non-optional ones... thus making non of them optional http://code.google.com/p/chromium/issues/detail?id=25001
Chrome Version : Trunk/Dev Channel/Beta Channel Extensions API methods have optional params before non-optional ones... thus making non of them optional (see Tabs and Windows apis in extension_api.json). You can't list optional params before non-optional ones. What steps will reproduce the problem? 1. Call a method like chrome.tabs.getSelected(callbackFunction) and leave off the windowId (which should be optional). 2. See a JS exception thrown because the callbackFunction is expected to be the integer windowId. What is the expected result? That the API's be arrange with non-optional parameters first in the method signature. What happens instead? Please provide any additional information below. Attach a screenshot if possible. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
