[cairo-bugs] [Bug 54549] New: caitro_close_path should not change extents on a "empty" path

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54549

             Bug #: 54549
           Summary: caitro_close_path should not change extents on a
                    "empty" path
    Classification: Unclassified
           Product: cairo
           Version: 1.12.2
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: cworth at cworth.org
        ReportedBy: jku at linux.intel.com
         QAContact: cairo-bugs at cairographics.org


This code:
    cairo_move_to (cr, -1, 1);
    cairo_path_extents (cr, &x1, &y1, &x2, &y2);
    printf ("extents before close_path: %f %f %f %f\n", x1,y1,x2,y2);
    cairo_close_path (cr);
    cairo_path_extents (cr, &x1, &y1, &x2, &y2);
    printf ("extents after close_path: %f %f %f %f\n", x1,y1,x2,y2);
will output
    extents before close_path: 0.000000 0.000000 0.000000 0.000000
    extents after close_path: -1.000000 0.000000 0.000000 1.000000

That seems like a bug to me: Shouldn't the boundingbox still be zero sized
after cairo_close_path().

This started happening at commit 166453c1ab.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.