Jan Henning 951c14aa26 Bug 1414084 - Part 2 - Use UUIDs for the NativeWindow menu API, too. r=Grisha ... At the moment, the code for handling of JS-created main menu items is more or less duplicated between the old NativeWindow API and Webextensions, with the only real difference being that the former communicates directly via menu item IDs, while the latter uses UUIDs for messaging between Gecko and the UI. By switching the NativeWindow API to using UUIDs as well, we will be able to start unifying this code again. As for backward compatibility - the return value of NativeWindow.menu.add is valid for the current session only, so no migration is necessary - the return value of NativeWindow.menu add was already effectively only an opaque value which only had real meaning for subsequent calls to menu.add, menu.update and menu.remove, so it shouldn't really matter whether we return a plain numeric ID or an UUID in string form - old-style add-ons are now unsupported for better or for worse and our one in- tree caller won't have any problems with this change MozReview-Commit-ID: HdRNhrx1pu7 --HG-- extra : rebase_source : 33ce855ac2f2f65fe20cb5047de3b8cbbcd094d9		2018-03-18 13:26:16 +01:00
..
android	Bug 1414084 - Part 2 - Use UUIDs for the NativeWindow menu API, too. r=Grisha	2018-03-18 13:26:16 +01:00
locales	Merge inbound to mozilla-central. a=merge	2018-08-02 01:09:38 +03:00