Kozea/WeasyPrint

Dotted borders require a lot of PDF paths

Open

#2,526 opened on Aug 15, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (6,291 stars) (630 forks)batch import
good first issueperformance

Description

Tested under windows 11 with Weasyprint 65.1 and 66

66: 33.6 KB 65.1: 3.74 KB

<!DOCTYPE html>
<html>
  <head>
    <style>
      body {
        border: 1px dotted black;
      }
    </style>
  </head>
  <body>
  </body>
</html>

Contributor guide

Tech stack
pythoncss
Domain
performance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
HTMLCSSPythonWeasyPrint basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the border rendering code, likely in WeasyPrint's draw module (e.g., `weasyprint/draw.py` or similar). The issue is that dotted borders generate an excessive number of PDF path objects. Look for how the border style is translated to PDF paths and consider optimizing by using fewer path segments or a different PDF primitive. Check existing comments in the issue for any hints. A solution might involve grouping adjacent dotted segments or using a different dash pattern.