[Bug]: fluent-text-field broken in 3.0.0

[jpenniman-ci]

Component

Field

Package version

3.0.0

@microsoft/fast-element version

?

Environment

.Net 10, Razor pages

Current Behavior

Since the CDN updating to 3.0.0, fluent-text-field are no longer rendering. Were they replaced with fluent-text-input?

Expected Behavior

The field should render and allow input.

Reproduction

Just add the component to a form. You'll see it doesn't work.

Steps to reproduce

Create a new razor project, add FluentUI, and add a fluent-text-field.

Are you reporting an Accessibility issue?

No response

Suggested severity

Urgent - No workaround and Products/sites are affected

Products/sites affected

No response

Are you willing to submit a PR to fix?

yes

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[jarfer]

Hi all sorry I was lead here because 3,0.0 is totally broken for me

I'm working on a web project, (uses many different types) up to now been good fired it up today and literally nothing works at all. Yes Text inputs are broken, Selects are too, and I think button sare mostly broken

So drastic and broad are these breakages that I simply reverted web project to use previous version and everything perfect

Neither Copilot nor myself have managed to get a single component working yet in 3.0.0l Copilot thinks none of the components are being registered or rendered (nothing about the fluent markup is being processed ) if this helps so it may well be all same cause. All components are invisible, selects churn their options into the page which the browser recognises as markup, but beyond this you won't see much at all I think

[jpenniman-ci]

Same. Most every component is broken. We had to rollback to 2.x. It might be a bad build?

[MarvinKlein1508]

@jarfer @jpenniman-ci pretty much all component names have been changed in cb3684e

You should get it back to work if you adjust the registry like we did in the Blazor wrapper for the components.
https://github.com/microsoft/fluentui-blazor/blob/cb4a3916bb010f762eeda34ab8604e9d6cefd836/src/Core.Scripts/src/FluentUIWebComponents.ts

[jarfer]

HI all, thanks this may be a misunderstanding on my part, yes I saw the name changes of components, I think what it may be: I'm not using React JS or Blazor on this particular project - previous versions worked fine on vanilla JavaScript and HTML on v2, but v3 doesn't appear to work outside of the React JS environment (I have already tried using the updated names of components) but suspect this may be what it is?

[chrisdholt]

Are you moving from v2 to v3 between the major versions? If so, this was a large-scale breaking change to align naming, attribute/properties, and design tokens to the official Fluent UI conventions.

[jpenniman-ci]

Are you moving from v2 to v3 between the major versions? If so, this was a large-scale breaking change to align naming, attribute/properties, and design tokens to the official Fluent UI conventions.

Yes. If that is the case, it should probably be documented in the change log as a breaking change.

[chrisdholt]

Are you moving from v2 to v3 between the major versions? If so, this was a large-scale breaking change to align naming, attribute/properties, and design tokens to the official Fluent UI conventions.

Yes. If that is the case, it should probably be documented in the change log as a breaking change.

Thanks for the feedback - we follow semver closely with regards to major, minor, and patch versions; it looks like we may want to look at the automated pipeline and see if we can prefix the commit messages accordingly for major specifically. The changelog for all of the Alpha and RC versions are here: https://github.com/microsoft/fluentui/blob/master/packages/web-components/CHANGELOG.md#change-log---fluentuiweb-components.

@radium-v is currently working on a detailed migration doc we hope to have out quickly.