chore: superseded by current-base focus PR #334 - #325
Conversation
📝 WalkthroughWalkthrough뷰어의 Changes포커스 표시 대비 계약
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/test_viewer_focus_appearance.py`:
- Around line 114-134: Update _focus_bands to parse the focus rule’s
outline-offset and account for it when processing the box-shadow band. Before
adding the shadow as a separate visible FocusBand, validate that the offset is
at least the shadow spread, or reduce the band width to only the exposed
portion, preventing overlapping outline and shadow widths from being summed.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7ceacc7f-f2ce-441b-ab3b-412d9f792623
📒 Files selected for processing (2)
scripts/test_viewer_focus_appearance.pysrc/main/resources/static/assets/viewer/viewer.css
|
@opencode-agent @cwl-noema-review Please independently review exact current head |
Pull request was closed
Superseded by clean current-base reconstruction
Closed in favor of PR #334.
PR #334 rebuilds the same bounded focus-appearance contract directly on protected
main55d7ae8647208e301f282350f076eeddaba61d11. Its exact changed blobs are:scripts/test_viewer_focus_appearance.py:ad1509e12b147582f6e3e824b9ff00fb34921b8e;src/main/resources/static/assets/viewer/viewer.css:3c19c3baccaaffdf1aa5277187591703aa8deb07.The current replacement head
d080540076703d2e94940522f18ac6be86d2da37is GREEN on CI31389256791, Security Scan31389256767, SAST31389256739, and fuzz31389256710; auto-merge is enabled through normal protection. The final commit changes no file content and exists only because the initial clean head had no Actions runs associated with it.Keeping both PRs would duplicate identical path ownership, review traffic, and merge risk. Issue #324 remains the product/standards authority until the protected replacement integrates.