Change Details

Blender Version: 3.1.2 **Short description of error** To my knowledge, the term Render Border is (or will be) deprecated. It used to be what is now called Render Region and had the same meaning. Some operators still use that term though. **Exact steps for others to reproduce the error** in 3DView, hit F3 and type "border". There are 5 results: - "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here. - "Reset Render Border": should definitely use the term Region - "Clipping Region": unrelated to Render Region, but python operator name uses "border" while the UI name uses "Region" (API compatibility reasons?) - "Set Render Region": same here, python name uses "border", UI name uses "Region". Keeping the legacy term in the API makes sense to not break add-ons and such, though eventually it should be consistent with the UI. Note: Changing to "Region" was a great decision imo, as its meaning is much more explicit than Border.

Blender Version: 3.1.2 **Short description of error** To my knowledge, the term Render Border is (or will be) deprecated. It used to be what is now called Render Region and had the same meaning. Some operators still use that term though. **Exact steps for others to reproduce the error** in 3DView, hit F3 and type "border". There are 5 results: - "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here. - "Reset Render Border": should definitely use the term Region - "Clipping Region": unrelated to Render Region, but python operator label uses "border" while the UI name uses "Region" (API compatibility reasons?) - "Set Render Region": same here, python name uses "border", UI name uses "Region". Keeping the legacy term in the API makes sense to not break add-ons and such, though eventually it should be consistent with the UI. Note: Changing to "Region" was a great decision imo, as its meaning is much more explicit than Border.

Blender Version: 3.1.2 **Short description of error** To my knowledge, the term Render Border is (or will be) deprecated. It used to be what is now called Render Region and had the same meaning. Some operators still use that term though. **Exact steps for others to reproduce the error** in 3DView, hit F3 and type "border". There are 5 results: - "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here. - "Reset Render Border": should definitely use the term Region - "Clipping Region": unrelated to Render Region, but python operator namelabel uses "border" while the UI name uses "Region" (API compatibility reasons?) - "Set Render Region": same here, python name uses "border", UI name uses "Region". Keeping the legacy term in the API makes sense to not break add-ons and such, though eventually it should be consistent with the UI. Note: Changing to "Region" was a great decision imo, as its meaning is much more explicit than Border.