fix: trim whitespace in polygon clip-path point parsing

Fixes #763

The parsePolygon function split comma-separated points without trimming
whitespace first. When CSS like 'polygon(100% 0, 81.844% 100%)' was
parsed, the space after each comma created a phantom empty-string element
during the subsequent .split(' '), causing x-coordinates to be resolved
against height instead of width for all points except the first.

This was invisible in tests because existing tests used square elements
(width === height). Adding .trim() before .split(/\s+/) ensures correct
index mapping for the width/height resolution.

Author: marceli1404

.husky/pre-commit

@@ -124,7 +124,8 @@ export function createShapeParser(
         .split(',')
         .map((v) =>
           v
-            .split(' ')
+            .trim()
+            .split(/\s+/)
             .map((k, i) =>
               lengthToNumber(
                 k,

src/parser/shape.ts

@@ -104,6 +104,25 @@ describe('clipPath', () => {
     expect(toImage(svg)).toMatchImageSnapshot()
   })
 
+  it('should render polygon clip-path correctly on non-square elements', async () => {
+    const svg = await satori(
+      <div
+        style={{
+          height: '100%',
+          width: '100%',
+          display: 'flex',
+          alignItems: 'center',
+          justifyContent: 'center',
+          backgroundColor: '#fff',
+          clipPath: 'polygon(100% 0, 81.844% 100%, 0 100%, 18.156% 0)',
+        }}
+      />,
+      { width: 180, height: 100, fonts }
+    )
+    const image = toImage(svg)
+    expect(image).toMatchImageSnapshot()
+  })
+
   it('should respect left and top', async () => {
     const svg = await satori(
       <div