feat: Update Blazor Wrappers to FluentUI Web Components v3

[EisenbergEffect]

🙋 Feature Request

🤔 Expected Behavior

All components visually align with official FluentUI design system specifications and interop with the token system.

😯 Current Behavior

Minor visual differences exist between versions of the components due to previous product non-alignment.

💁 Possible Solution

Products have now aligned and visual representations in the FluentUI Web Components can be updated to match.

[EisenbergEffect]

The core component work is in progress now. We'll update this issue when the work is ready for Blazor integration.

[ObeA]

We have noticed there are still some differences between the design kit (and the React implementation) of Fluent UI and the Blazor wrappers.

What is the status of this issue?

[EisenbergEffect]

I don't work for Microsoft anymore. I left almost a year ago. So, I don't know entirely what's going on right now. @chrisdholt may be able to shed some light on the situation.

[chrisdholt]

Latest effort is here https://web-components.fluentui.dev/, currently in "Beta". There's likely work to do to get Blazor updated, @vnbaaij is likely best for that effort.

[Seanxwy]

What is the progress so far?

[vnbaaij]

What is the progress so far?

Not much/very little.

The web components team is close to delivering a 'single script' version (ie a single web-components.js file like we have now). Only once we have that, we can make a start with looking at what needs to happen on our side (which I expect to be quite a bit).

What we do know is that this web components v3 based version will be a major release from us. Expect lots of breaking changes, and also, missing components. The set of components the team is targeting for v3 is smaller than what we had with v2

[DanielCordell]

The set of components the team is targeting for v3 is smaller than what we had with v2

Is this with the goal of eventual parity and just having an initial smaller release, or are some components being permenantly thrown out?

I can't seem to find any discussions on this topic in the main fluent repo, can you post a link?

[chrisdholt]

The set of components the team is targeting for v3 is smaller than what we had with v2

Is this with the goal of eventual parity and just having an initial smaller release, or are some components being permenantly thrown out?

I can't seem to find any discussions on this topic in the main fluent repo, can you post a link?

The immediate goal will be parity with Fluent 2 Specs - there are some things which aren't yet represented there. It doesn't mean they can't exist, but we'd likely need requests so we can get the design team to come up with a Fluent 2 design.