now the restful api : /vtibin/ExcelRest.aspx/xxx.xlsx/model/Ranges("abc")?$format=html generated the html with div and position:absolution style. This fragment can not display in outlook email well.

Hi,
I want to add the multiple root folders to existing documents library along with custom fields but I didn't see any mentioned verb to create the sp folder in document library.

Examples, tutorials on PeoplePicker for SharePoint Online; populating columns with the different Values

Allow users to specify multiple permissions in webApiPermissionRequests that admin can approve only some of them (not all or nothing).

Also would be great if the application can request more/different permissions based on user configuration during runtime:
Make a request to resource X
Get access denied
Prompt the user and open a new "request" for that resource during runtime

When using the AadHttpClient within a SPFx WebPart, a popup appears that is currently necessary to facilitate authenticate to Azure AD (part of ADAL JS). While this is understandable if the user needs to supply additional authentication components, if the user has the necessary rights to the Azure secured API, no popup should be presented.

Scenarios where this behavior is not acceptable:
- Pages with multiple third party data sources (user is bombarded with popups)
- High traffic landing pages (like corporate home pages) where look & feel are crucial

Documentation on behavior:
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aad-tutorial

GitHub Issue relating to this:
https://github.com/SharePoint/sp-dev-docs/issues/1471

When a page event occurs. Allow the webpart to get this action and dismiss it, e.g. ‘No you can’t publish this page until this property is equal to x’

Currently there is no way to control feature activation in SPFX solutions. Features always gets activated even if its needed on demand.

The OData v3 specification (which I believe the SharePoint REST API is supposed to be v3) supports an operator to include the total row count for a query in the response. The Project Online /api/ProjectData endpoint supports it as well. However it seems the /api/Lists endpoint does not for some reason.

Could you "fix" this so the Lists API is OData compliant?

See section 10.2.3.6 here: http://www.odata.org/documentation/odata-version-3-0/odata-version-3-0-core-protocol/

Currently SPFx build process assumes that project only has one config.json and one package-solution.json file. For projects that are deployed to multiple tenants this limitation should be removed.

Easiest way would be to add some build parameters that can be used to override locations of those files. e.g.
gulp package-solution --ship -solutionfile mycustomfolder/package-client1.json

There is no need to limit View Threshold when querying against REST or CSOM. Remove the Threshold in order to pull large data.

Right now in the SharePoint Online Client APIs (Whether it is CSOM or REST) we can't change the CalendarSettings properties to override the current Overlay Calendar of a View.

It used to be doable in SharePoint 2010/2013, but on SharePoint Online CSOM there is no CalendarSettings member of the View.

The closest we can get it the HtmlSchemaXml which includes the AggregationCalendars node but it's read only.

Possible to add/remove/list Labels to document Library , via REST/CSOM/JSOM

Under apps From Your Organization, we can not distinguish apps from
Site Collection App Catalog and apps fromTenant App Catalog.

Ability to mash up multiple IFrame hosted Office app web pages with IPC between them

The ability to both read and write to the various property bags would be very helpful. Currently it's possible to read from a web property bag, but not to write. It'd be even better if the other property bags supported this.

Make SPFx projects compatible with TSLint VSCode extension by either moving the tslint.json file to the root folder or by creating a new tslint.json at the root that instructs the VSCode extension to look for rules on the config folder

Please, make it possible to use SharePoint Extensions on Classic sites in order to use common components throughout the tenant. A good example is the Footer, we want to use the same footer so we don't have to build two different components in two different technologies.