Summary
In patch-mark@1.0.0, a resolved annotation renders the check SVG at nearly the full width of the annotation card instead of at badge size.
Reproduction
- Mount
<patch-mark> with a store that supports update().
- Create an annotation.
- Resolve it, or load it with
status: "resolved".
- Open the annotation list.
Actual behavior
The checkmark inside .pm-item-status expands into a very large icon. In a 396 px-wide panel, the live computed SVG dimensions were 234.219 × 234.219 px.
The resolved badge markup is:
<span class="pm-item-status">
<svg viewBox="0 0 24 24">…</svg>
已解决
</span>
.pm-item-status styles the badge container, but does not constrain its child SVG. The action icons do have an explicit rule:
.pm-item-actions button svg {
width: 0.78rem;
height: 0.78rem;
}
Expected behavior
The resolved checkmark should remain a compact inline badge icon.
Suggested fix
.pm-item-status svg {
width: 0.75rem;
height: 0.75rem;
flex: none;
}
A regression test should assert that the resolved-status SVG receives an explicit bounded width and height.
Summary
In
patch-mark@1.0.0, a resolved annotation renders the check SVG at nearly the full width of the annotation card instead of at badge size.Reproduction
<patch-mark>with a store that supportsupdate().status: "resolved".Actual behavior
The checkmark inside
.pm-item-statusexpands into a very large icon. In a 396 px-wide panel, the live computed SVG dimensions were234.219 × 234.219 px.The resolved badge markup is:
.pm-item-statusstyles the badge container, but does not constrain its child SVG. The action icons do have an explicit rule:Expected behavior
The resolved checkmark should remain a compact inline badge icon.
Suggested fix
A regression test should assert that the resolved-status SVG receives an explicit bounded width and height.