Thanks for this idea @ipeerbhoy this issue was addressed in ArcGIS Pro 3.4. Are you working in an earlier version? Let us know if you are not seeing this behavior in ArcGIS Pro 3.4 or above. This fix is also included in patches 3.2.5 and 3.3.3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.