Instead of using TypeScript and JavaScript to develop SPFx webparts give an option to write webparts with Blazor and C#

Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.

The idea is to have full control on user interaction with components.

In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...

Ideally to have access to domElement and data model of component.

I want to truncate the string which crosses the width and add '...' at the end. Currently I am able to do that except for adding the '...'. It can be done if the column formatter supports 'text-overflow: ellipsis'.

Once the Sharepoint Space has been rolled out among all tenants, it would be nice to have a wider and especially accessible 3D data format range.

Regarding Architectural, Engineering, and Construction objects, there is a global open standard based on 3D smart objects called IFC (Industry Foundation Classes), developed by buildingSMART International (+ info https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/ )

It would be a consistent approach from Microsoft to implement this 3D format in Sharepoint Spaces since is a global and open Standard.
https://support.microsoft.com/en-us/office/add-a-3d-object-to-a-sharepoint-space-6e17e4d4-cad1-459d-90ce-01540697214b

Simply hide the page canvas until all SpFx WebPart promises have resolved for modern sites

This would conceivably
1. Improve page load performance by not forcing the browser to display several loading gifs/fading animations at the same time
2. Improve user experience by displaying a complete page to the user rather than the page "jumping" constantly during the first 3-10 seconds of loading
3. Allow developers to add minor CSS updates to the page prior to render using the SharePoint Framework without noticeable "jumping"

When creating sites using a site design (recipe), one of the available verbs is calling an HTTP-triggered Flow to perform some additional configuration on the newly created site.

When installing SPFx solutions in a site, we should similarly be able to specify an HTTP-triggered Flow to be called as a part of the installation process. This would not only allow developers to provision configuration beyond what's currently supported with Feature XML, but also create a consistent development experience across the different workloads (site designs vs. SPFx).

I understand the SPFx web parts are running in the user’s context. It would be helpful if the new framework has the target audience property

Observed behavior

When using a monorepo manager, like for example @microsoft/rush, the rush build command bundles all projects which are referenced in the monorepo - including SPFx projects.
When running gulp serve in (one of) the SPFx project(s), the bundle gulp command rebuilds the project. This is an unnecessary step, which would be nice if we could disable.

Proposed solution

Add a --nobuild flag support to the gulp serve command so we can start the local web server without rebuilding the SPFx code.

Listview CommandSet extension - Should be able to create custom commanbar button in the listview commandbar with sub-menu options like it is available for default buttons on the command bar.

The latest version of the SharePoint Framework Yeoman generator contains a mix of features that are GA and preview features (for example connecting to MS Graph, web part connections, extensions). Whether the generated solution can be run in production depends on the features used to build the web part. With that, when bundling the project, the toolchain should warn of any experimental features being used in the project which would prevent the solution from being deployed to production tenants. This would help developers avoid deploying solutions depending on experimental features to production tenants, only to see the deployment fail.

Currently there are no ways we can have a group created for custom SPFx webparts developed. We have to use the existing groups mentioned here, https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries#predefined-modern-groups. Need to have ability to have custom groups for Webparts

It would be great to add commands to the command set of a modern page, with similar events to list view extensions e.g. onListViewUpdated > onPageUpdated, and onExecute.

The API should enable easy and reliable access to important page information like field data, published state, whether it is promoted as news, etc.

SharePoint Add-In AppWeb Document Library allows to create PowerPoint however once it is created, you click on the PowerPoint and it does not render. it throws an error. Word, Excel works fine however this might be an issue with OWA Office Web Apps and PowerPoint Online. This issue started appearing from Jan 2018 across all Office 365 tenants. Is there any resolution from Microsoft on this? https://techcommunity.microsoft.com/t5/SharePoint-Developer/Can-t-open-PowerPoint-files-from-a-Library-inside-an-Add-In/m-p/163739#M4419

Allow to call out of the box render for cell in custom field customizer.

Use case:
based on user permissions render out of the box LinkTitle cell or custom copmonent with additional logic.

This scenario is needed for all types of fields that are rendered as complicated HTML, not just text (LinkTitle, User or Group fields, etc.)

At the moment custom property pane controls cannot invalidate the whole property pane. This means if you enter an incorrect value for your custom input, the property pane will still apply it (or the apply button will be enabled).

It would be great to have a way to make it possible to invalidate the property pane like the OOTB property pane controls. This would have a huge benefit for all the controls of the @pnp/spfx-property-controls (https://github.com/SharePoint/sp-dev-fx-property-controls) project which is used in a lot of projects.

More details for this can be found in this issue on Github: https://github.com/SharePoint/sp-dev-docs/issues/3440

HTML responsive design principles should be used for all pages. All elements within modern pages should implement simple concept of HTML responsive design.
Tables lack width lock with width & height of viewscreen, nor does allow to set fixed (or percentage, or em/px) widths per whole table, or individual column or line.
Currently this limitation heavily impact UX on any published modern pages, hence the read does not always see the whole published content (if window size is more narrower that the page/table size).

In the classic experience it's possible to hide ribbon buttons and menu options in the ECB. In the modern UI this currently isn't possible.
Please add support to also hide OOTB List View Command Set buttons and ECB items in the modern UI.

In the Classic view this could be done by a Custom Action:

<CustomAction
Id="RemoveRibbonButtonLibrary"
Location="CommandUI.Ribbon"
RegistrationId="101"
RegistrationType="List">>
<CommandUIExtension>
<CommandUIDefinitions>
<CommandUIDefinition Location="Ribbon.Library.Actions.ExportToSpreadsheet" />
</CommandUIDefinitions>
</CommandUIExtension>
</CustomAction>

But this currently doesn't work for the Modern UI.