Bug reportNov 16, 2026· 0:24· 19 views
FluentUI web-components: fluent-button stays disabled after fieldset is re-enabled
0:24 total
Comments · 0
Be the first to comment.
Bug reportby SceneRecap AI
mediumfluent-button form-associated disabled handling, likely formDisabledCallback or the fieldset disabled-state sync not clearing the disabled state when the ancestor fieldset is re-enabled.
page: Bug repro page with a fluent-button and a native button inside a fieldsetpackage: @fluentui/web-components v3.2.1related_issue: github.com/microsoft/fluentui/issues/37047
Repro steps
- 1.Open the repro page. A fluent-button and a native button sit inside a fieldset labeled 'Inside the fieldset'. Both show ENABLED.
- 2.Click 'Disable fieldset' to set fieldset.disabled = true.
- 3.Click 'Re-enable fieldset' to set fieldset.disabled = false.
- 4.Observe the state of the fluent-button and the native button.
Expected
When fieldset.disabled is set back to false, the fluent-button returns to the enabled state, the same as the native <button>.
Actual
After the fieldset is re-enabled, the native <button> shows ENABLED again. The fluent-button still shows DISABLED and stays that way through the end of the recording.
Evidence
visualInitial state: both Fluent button and Native button show ENABLED badges. Status reads 'Initial state: Both buttons enabled inside the fieldset'.
visualAfter 'Disable fieldset' is clicked, both buttons show DISABLED badges. Status reads 'Step 1 ✓ fieldset.disabled = true, both buttons disabled (expected)'. The disable step works as expected.
visualWhile disabled, the Native button label is greyed out but the Fluent button label is not visually greyed out, even though its badge reads DISABLED.
visualControl case: after re-enable, the native <button> returns to ENABLED with a green outline. Native behavior is correct.
visualFailing case: after re-enable, the fluent-button still shows DISABLED with a red outline. Status reads 'Step 2 ✕ BUG: fieldset.disabled = false, native <button> re-enables, but fluent-button stays stuck in disabled state'.
visualFluent button still shows DISABLED at the end of the recording. The state never recovers.
Issue markdown (copy-paste ready)
## fluent-button stays disabled after parent fieldset is re-enabled **Package:** @fluentui/web-components v3.2.1 **Related:** github.com/microsoft/fluentui/issues/37047 ### Steps to reproduce 1. Place a `<fluent-button>` and a native `<button>` inside a `<fieldset>`. Both start enabled (0:01). 2. Set `fieldset.disabled = true` by clicking 'Disable fieldset' (0:07). 3. Set `fieldset.disabled = false` by clicking 'Re-enable fieldset' (0:13). 4. Check the state of both buttons (0:15). ### Expected Both buttons return to the enabled state when the fieldset is re-enabled. ### Actual The native `<button>` re-enables. The `<fluent-button>` stays in the disabled state (0:13 to 0:23). ### Evidence - 0:01: Both buttons show ENABLED. - 0:07: Both buttons show DISABLED after the fieldset is disabled. This step works as expected. The native button label is greyed out but the Fluent button label is not visually greyed out. - 0:13: Control: the native `<button>` shows ENABLED again. Failing case: the `<fluent-button>` still shows DISABLED. The status reads 'Step 2 ✕ BUG: fieldset.disabled = false, native <button> re-enables, but fluent-button stays stuck in disabled state'. - 0:23: The fluent-button is still DISABLED. It never recovers. ### Suggested area The form-associated disabled handling in fluent-button (for example `formDisabledCallback`). The disabled state is applied when the fieldset is disabled but is not cleared when it is re-enabled. *Recorded with SceneRecap.*
Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →