[Webkit-unassigned] [Bug 48516] New: GraphicsContext: Remove "current path" and have strokePath, fillPath and clipPath take a Path argument

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 28 06:00:18 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=48516

           Summary: GraphicsContext: Remove "current path" and have
                    strokePath, fillPath and clipPath take a Path argument
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: kling at webkit.org


GraphicsContext currently has a "current path", set using GraphicsContext::beginPath() and GraphicsContext::addPath()

This path is then implicitly used by strokePath(), fillPath() and clipPath(). To make it more confusing, due to a quirk of CGContextStrokePath, strokePath() is expected to clear the current path. This is poorly handled ATM, for example there is some mysterious Skia-specific code handling the case in RenderSVGResourceSolidColor::postApplyResource().

I propose we refactor GraphicsContext to take a Path object as an argument to these functions and remove the concept of a "current path."

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



More information about the webkit-unassigned mailing list