You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.
When the border-width for an element is larger than the border-radius for one or more of its corners, then that corner will be rendered with some extra "bumps" sticking out from it. This is due to the fact that the calculated path ends up crossing itself in the corners, and the quadratic curve gets drawn concave rather than convex.
This is easily seen in some of the IE9 border-radius testcases, e.g. border-radius-sum-of-radii-001.htm
The text was updated successfully, but these errors were encountered:
- Box path calculation has been improved to ensure a correct (squared) path when the shrink is greater than the radius.
- Rewrote border renderer to use only fills with "eofill" subpaths to make the cut-outs for dashed/dotted/double styles.
- Dashes are now centered along the edge like WebKit does.
- Removed all logic around VML stroke as it is no longer used.
- Flattened the getBoxPath method signature to avoid unnecessary transient object creation.
Fixes issue #11
When the border-width for an element is larger than the border-radius for one or more of its corners, then that corner will be rendered with some extra "bumps" sticking out from it. This is due to the fact that the calculated path ends up crossing itself in the corners, and the quadratic curve gets drawn concave rather than convex.
This is easily seen in some of the IE9 border-radius testcases, e.g. border-radius-sum-of-radii-001.htm
The text was updated successfully, but these errors were encountered: