RequiresSmoothRendering is always false for an SvgRectangle if CornerRadiusX and CornerRadiusY are 0

Description

Anti-aliasing is never used for a simple rectangle without rounded corners, but forcing anti-aliasing to be enabled improves the rendering. I do not quite understand the reasoning for the logic in SvgRectangle.

Currently, RequiresSmoothRendering is implemented like this:

        protected override bool RequiresSmoothRendering
        {
            get
            {
                if (base.RequiresSmoothRendering)
                    return (CornerRadiusX.Value > 0.0f || CornerRadiusY.Value > 0.0f);
                else
                    return false;
            }
        }

But this would make more sense to me (no matter what base.RequiresSmoothRendering returns, force it on if corners are rounded):

        protected override bool RequiresSmoothRendering
        {
            get
            {
                if (!base.RequiresSmoothRendering)
                    return (CornerRadiusX.Value > 0.0f || CornerRadiusY.Value > 0.0f);
                else
                    return true;
            }
        }

Example data

SVG	svg-net rendering
Rectangles
Rectangles with corner radius

When the original svg is rendered to a small bitmap the spacing and bottom vertical alignment does not appear to be consistent, but the rendering is improved when anti-aliasing is forced to be on by adding a very small corner radius to the rectangles.

Used Versions

SVG 3.3.0 .NET Framework 4.8

[mrbean-bremen]

Ok, I did a few tests, and Chrome, FireFox and Edge agree on the handling (IE seems not to handle shape-rendering). If shape-rendering is set to auto or geometricPrecision, they use anti-aliasing for the rectangles, if set to optimizeSpeed or crispEdges they don’t use it, regardless of rounded edges. The same seems to be true for other shapes. So to conform to these, we would have to change the base implementation to use anti-aliasing also for geometricPrecision, and remove the overload for Rectangle. Any thoughts?

[mrbean-bremen]

Consider fixed, as it now bahaves like in browsers, and the standard is not very specific about the implementation.