Webcomponents V3

[MarvinKlein1508]

Hey @vnbaaij

I just thought I might ask you. Is there any roadmap or information about the current state of the webcomponents v3?

I can only find this dev site:
https://web-components.fluentui.dev

And this branch which hasn't been updated in the past 6 months.
https://github.com/microsoft/fluentui/tree/web-components-v3

Where can we get some information about it?

[dvoituron]

About the new FluentUI Web Component, you have:

• The current roadmap: https://github.com/orgs/microsoft/projects/652/views/2
• The source code: https://github.com/microsoft/fluentui/tree/master/packages/web-components/src
• Our FluentUI-Blazor branch: https://github.com/microsoft/fluentui-blazor/tree/dev-v5

But no release date has yet been published.

[MarvinKlein1508]

Hi @dvoituron

thanks this helps a lot! :)

[amather]

Hey @dvoituron @vnbaaij ,

Just found the thread and wanted ask follow up questions, mainly what you expect from v3 and and what we end-users can expect from the future update?

The way I see it, until now, web-components wrapped fast-foundation, a project that was effectively discontinued and is no longer supported. The new web-components v3 will therefore be a full rewrite implying that incorporating v3 into fluentui-blazor will be a major task for you and a major update for us end users.

Is my view correct? If so, I'd be even more interested in your thoughts... e.g. is it even feasable to plan for a migration guide if changes are that extensive? Or do you expect API compatibility, so impact is managable?

Thanks!

[vnbaaij]

The way I see it, until now, web-components wrapped fast-foundation, a project that was effectively discontinued and is no longer supported. The new web-components v3 will therefore be a full rewrite implying that incorporating v3 into fluentui-blazor will be a major task for you and a major update for us end users.

Yes, the FAST team deprecated fast-foundation and they are sort of rewriting the web components for v3 (which still uses FAST technology stack internally!). That on it self does not make incorporating v3 in Fluent UI Blazor a major task. What does make it a major task is that a lot of attribute and property names are changing. This is not because of the rewrite but because the Fluent Web Components are getting aligned to the Fluent UI React components in that area.

Is my view correct? If so, I'd be even more interested in your thoughts... e.g. is it even feasable to plan for a migration guide if changes are that extensive? Or do you expect API compatibility, so impact is managable?

For you as end users there will be breaking changes when moving from v4 to v5. It will most definitely not be a matter of installing the new package and be done. Where possible, we will deliver guidance, docs and tools/utilities but it is not our main goal to make this a one-step-super-easy upgrade. For a look at the current status and how we do migration notes, see https://fluentui-blazor-v5.azurewebsites.net/MigrationV5

In fact, I don't think it will be a 'real' upgrade at all in the first period of v5 availability. The Web Components v3 release will not include all v2 Web Components in its initial release. The set will grow over time but some components might not return at all. It will strongly depend on what components you are using in your project if you can migrate directly, later or, in a worst case scenario, not at all,

ps. Due to the technical issues it is not/will not be possible to use V2 & V3 Web Components side-by-side