Referred style sheet stays dirty after saving when using the UIBuilder

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 6000.3.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 6000.2 port as this issue will be resolved in a newer release. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 6000.1 port as this issue will be resolved in a newer release. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 6000.0 port as this issue will be resolved in a newer release. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.

Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

2023.1 is no longer a supported version of Unity. Please see the corresponding 2023.2 port instead (if applicable).

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2022.3.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.

Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 2021.3.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.