Values of SvgPathSegment became relative (not absolute as earlier) when iterating through the SvgPathSegmentList about svg HOT 3 OPEN

Was the change intentional? I did not find any breaking changes in the release notes.

Yes, see #925. And yes, the release notes for this are not really helpful in that respect.

Is there a flag or a setting I can use to return the default behavior to absolute coordinates without the need to calculate them manually?

Not that I know of, though @H1Gdev might know more.

from svg.

Workaround that I've currently implemented in my project:

PointF absolutePoint = new PointF(0, 0);
foreach (var point in path.PathData)
{
     absolutePoint = ToAbsolute(point.End, point.IsRelative, absolutePoint);
     ... do what you need to do with the absolutePoint
}

Where ToAbsolute I took from the abstract class SvgPathSegment

 protected static PointF ToAbsolute(PointF point, bool isRelative, PointF start)
 {
     if (float.IsNaN(point.X))
         point.X = start.X;
     else if (isRelative)
         point.X += start.X;

     if (float.IsNaN(point.Y))
         point.Y = start.Y;
     else if (isRelative)
         point.Y += start.Y;

     return point;
 }

from svg.

@hubaksis

In the previous version, relative information was lost when read SVG into DOM.
(SVG(relative) -> SvgDocument(absolute) -> SVG(absolute))

We supported relatives with PR #925.

For conversion, I think you should use ToAbsolute logic. You can calculate each point in this method sequentially.

from svg.