Blueprint Diff tool does not mark changed properties as having been changed if they are in a custom nested category

The Blueprint Diff tool does not highlight properties that have been changed from a previous version of the Blueprint if those properties are contained in a custom nested category.

REGRESSION:
No. This behavior also occurred in 4.18.3.

1. Create a new Basic Code project.
2. Add a new Actor code class to the project.
3. In the body of the Actor class, add a UPROPERTY of any type, using the EditDefaultsOnly specifier and custom nested categories.
   • eg: UPROPERTY(EditDefaultsOnly, Category = "TestCat|NewCat")
4. Set up the project to use Git source control.
5. Create a new Blueprint derived from the new Actor code class.
6. Submit the new Blueprint to source control.
7. Open the Blueprint and make changes to the default values for the property added in step 3.
8. Compile and save the Blueprint and submit it to source control.
9. Repeat steps 7 and 8 one or two more times.
10. Open the source control history for the Blueprint.
11. Select the most recent version of the Blueprint and diff against the previous revision.
12. Locate the property in the Defaults section.

RESULT:
None of the values that were changed are highlighted as having been changed from the previous version of the Blueprint.

EXPECTED:
The changed values are highlighted as having been changed since the previous version of the Blueprint.

WORKAROUND:
Do not use custom nested categories.