This is a follow-up to ticket #10904, where the fix was confirmed for version 10.7. #10951

4 Answer(s)

• 

  0

  AI-Bot created 4 hours ago

  Support Team ABP Agent

  • What you’re observing in @volo/abp.commercial.ng.ui 10.7.0 is consistent with the original regression: the lookup component still has a signal-driven disabled input mirrored via an effect(...), and the inherited setDisabledState(...) path still doesn’t trigger view refresh (markForCheck()), so a reactive-forms disable can be lost/overwritten.
  • Based on the only verifiable support information available (the original ticket thread), ABP support first stated “the fix will be included in 10.7”, but later clarified: “We’ll fix this in a future release.” There is no verified public info (release note / commit / tag) that specifies which exact version after 10.7.0 contains the permanent fix.

  What you should do now (until the permanent fix is released)

  1. Keep using one of these workarounds:

     • Template workaround: bind [disabled] to the form/form-control disabled state.
     • Or the main.ts prototype patch from ticket #10904 (the one that merges _inputDisabled + _formDisabled and calls cdRef.markForCheck() in setDisabledState).

  2. Open a new support ticket (as you did) and reference that:

     • You’re on 10.7.0 and the issue persists.
     • The published bundles still contain the effect(() => this.disabled = this.disabledInput()) behavior and setDisabledState still doesn’t markForCheck().
     • The main.ts patch from #10904 still fixes it. This will allow the ABP team to link it to their internal issue tracker and respond with the planned patch version (e.g., 10.7.1 / 10.7.2 / 10.8).

  Sources (validated)

  • https://abp.io/support/questions/10904/Regression--setDisabledState-reactive-forms-disable-no-longer-works-on-Lookup-components-after-upgrading-from-1011-to-1061

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  sserestyen created 4 hours ago

  Could the support team confirm when that issue will be fixed?

  Thanks, S.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 4 hours ago

  Support Team Fullstack Developer

  Hi,

  The fix was merged one day after 10.7.0 was published, so it missed that release. It will be in 10.7.1, which we plan to release next week.

  Until then, keep the workaround in main.ts. Remove it after upgrading to 10.7.1.

  Sorry for the confusion. Your ticket has been refunded.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  sserestyen created 3 hours ago

  [maliming] said: Hi,

  The fix was merged one day after 10.7.0 was published, so it missed that release. It will be in 10.7.1, which we plan to release next week.

  Until then, keep the workaround in main.ts. Remove it after upgrading to 10.7.1.

  Sorry for the confusion. Your ticket has been refunded.

  Thanks

  Ok, thanks for confirming it.

  S.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel