In the COM world using Ribbon XML it's possible to: 1) display built-in buttons in custom groups and 2) re-purpose built-in buttons. This way the UI can be optimized for the purposes of an add-in. (2) is especially important because Office applications don't expose very many events, making it difficult to impossible to know when a user has done something that requires a reaction from the add-in. In this regard, COM add-ins and VBA are still much more powerful than the JS APIs.

When you print a content add-in, an exact screenshot of the add-in’s current view is getting printed. This is unfavorable as all the UI/control elements you may use in your add-in (menus, buttons, navigation, etc.) get printed as well.

It would be so much better if Office could use the “screen” and “print” media types of CSS so you can hide specific elements (i.e. the UI ones) for the print-only appearance.

Add support for native .NET Core addins which will run on Windows and Mac platforms.

In VSTO, we can create Application-Level or Document-Level documents. In Office-JS, It seems that at the moment it is a mixture of application level for the ribbon/pane and workbook level for the JS.
This separation is important so developers can sell, for instance, a specific workbook for its own and only own ribbons and panes, or a generic applciation level tool.
A consequence of this request is that it should be possible to attach an office addin (initialization) to a specific document.

Currently it is possible to add only large sized icons in Office Addins ribbon.
It would be great to have smaller icon sized icons.

Currently we can't read or write enterprise custom fields that are defined on a project server or in project online. We only can write the predefined local custom Fields like Text1.

For enterprise scenarios like integrating with SAP or other ERP systems it is essential being able to read/write enterprise custom fields.

With VBA and VSTO this is possible, but those technologies are outdated by good reason, but closing the gap is essential to get rid of VBA and VSTO. Access to Enterprise Custom Fields is a major gap.

Microsoft Technet [1] describes exactly why this is a much needed feature: to prevent DNS spoofing at rogue networks (public Wifi, etc..) and protect Office365 users from malicious actions like credential theft.

DNSSEC is already widely deployed by many other major service providers.

[1] https://technet.microsoft.com/en-us/library/dn593670%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396#why

Please support time picker component nice look.

Facebook Group connector. The current facebook connector only connects to pages you own or like - but no to groups on facebook.

There should be an onClose event I can ask the user to save settings, or ask them if they are sure, and then prevent the close if necessary. If the add-ins are going to be useful business apps, the user experience of saving before closing is extremely important.

The save() methods that exists in the API's aren't aren't really very useful. This extends the typical Ctrl+S functionality. It would be great to implement a feature in which it would be possible for us to apply the save() method with a parameter: 'Url/path'. Currently it isn't possible for us to save a document to a specific location nor is it possible for us to load a document from a specific location.

Functions in topic:
- save(string url): apply url/path to where you wish to save the document.
- load(string url): apply url/path to a document you wish to load.

Currently, there is no ability to hide or show the task pane from the Office Javascript API.

Is there a way to specify, docking the task pane add-in in the manifest or any other manner. Default is always right, but few users need that In left hand side.

If not please suggest any possible solution

It would be very useful to have ability to open file from provided location or to save it there. This way developers could provide better cloud solutions.

Scenarios:
- Open file from or Save file to FileStream
- Open file from os Save file to provided URL (supporting http/ftp even secured)

See also: https://officespdev.uservoice.com/forums/224641-general/suggestions/13421412-allow-officejs-to-open-external-excel-workbook-pro

Support wildcards for AppDomains in Office add-in manifests to support sub domains for example <AppDomain>https://*.acme.com</AppDomain>

Supporting the Chrome Debugging Protocol on the embedded Webkit instance that runs in Office for Mac would make something like github.com/Microsoft/vscode-chrome-debug will be a viable debugger on the Mac.

There maybe alternatives to Chrome Debugging Protocol that I'm unaware of that can more easily be supported by VS Code. Either way, we are simply asking for a full fledged debugger (unlike Vorlon.js) that can plug in to the running add-in and set breakpoints, explore values etc.

When inserting ribbon icons into a word ribbon bar, couldn't customize the ribbon icons as we want. For an example when I add 3 buttons, it will appear as horizontal direction. But when I add 4 buttons one icon will appear as usual but other three as small icons for vertical direction. It would be great if we can customize ribbon icons through the API.

Please, add method for disabling/enabling built-in proofing tools