microsoft / microsoft/fluentui
[Bug]: Field missing "size" attribute
@chrisdholt is already working on this.
Since Aug 27, 2026.
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 46
Description
Component
Field
Package version
3.0.10
@microsoft/fast-element version
3.0.0
Environment
System:
OS: Linux 6.8 Debian GNU/Linux 13 (trixie) 13 (trixie)
CPU: (16) x64 AMD EPYC 9V74 80-Core Processor
Memory: 53.03 GB / 62.80 GB
Container: Yes
Shell: 5.2.37 - /bin/bash
Browsers:
Chrome: 148.0.7778.215
npmPackages:
@fluentui/react-components: 9.73.8 => 9.73.8
@fluentui/web-components: 3.1.0 => 3.1.0
@microsoft/fast-element: 3.0.0 => 3.0.0
Current Behavior
This is more of a request for information than a bug necessarily: I am wondering why the FluentField does not have an attribute on the component class for "size"? There is styling in the css that handles "size" being set, however, it does not show up in the CEM or on the storybook as an attribute. Is this intentional?
I could understand why this would be intentional, the component does not really need a property on the class and the overhead that comes with a FAST attribute, but in this case, perhaps the FluentField class doc should have an @attr jsdoc entry instead so the CEM is generated correctly?
Expected Behavior
FluentField should have a "size" attribute in CEM since it is handled like an attribute in terms of the API.
Reproduction
Not a bug with runtime behavior
Steps to reproduce
Not a behavior bug.
Are you reporting an Accessibility issue?
None
Suggested severity
Low - Has or doesn't need a workaround
Products/sites affected
Fabric UX
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.